Dem Armin sei Seidn

Dem Armin sei Schmierzettel

MusikzurNacht

leave a comment

Queen & David Bowie – Under Pressure (Classic Queen Mix) https://t.co/ZvK2czLt1s
from Twitter https://twitter.com/MusikzurNacht

September 17, 2016 at 11:12PM
via IFTTT

Written by Musik zur Nacht

September 18th, 2016 at 12:20 am

Posted in MusikzurNacht

Tagged with ,

MusikzurNacht

leave a comment

David Bowie – Heroes https://t.co/ZSCQ3EHGaa
from Twitter https://twitter.com/MusikzurNacht

September 17, 2016 at 11:11PM
via IFTTT

Written by Musik zur Nacht

September 18th, 2016 at 12:20 am

Posted in MusikzurNacht

Tagged with ,

MusikzurNacht

leave a comment


RT @geni256: Hammer! Der Drummer hat’s drauf! https://t.co/dCV7FBwsFA (FB: Congrats von M. https://t.co/0wh7JtULha)
from Twitter https://twitter.com/MusikzurNacht

September 17, 2016 at 12:47AM
via IFTTT

Written by Musik zur Nacht

September 17th, 2016 at 2:23 am

Posted in MusikzurNacht

Tagged with ,

MusikzurNacht

leave a comment


RT @BurgandySkies: https://t.co/8mDng9kuTu Been a long day. Just going to listen to this on repeat, k? @VNV_Nation #Perpetual #LetThereBeNeverEndingLight
from Twitter https://twitter.com/MusikzurNacht

September 16, 2016 at 07:32PM
via IFTTT

Written by Musik zur Nacht

September 16th, 2016 at 8:23 pm

Posted in MusikzurNacht

Tagged with ,

MusikzurNacht

leave a comment


Endlich mal gefunden. https://t.co/8YaPaWVPxH
from Twitter https://twitter.com/MusikzurNacht

September 16, 2016 at 07:30PM
via IFTTT

Written by Musik zur Nacht

September 16th, 2016 at 7:30 pm

Posted in MusikzurNacht

Tagged with ,

Windows IPv4 und IPv6

leave a comment

Quelle: https://support.microsoft.com/de-de/kb/929852
Quelle englisch (besser): https://support.microsoft.com/en-us/kb/929852

Text folgt ggf. noch 😉

How to disable IPv6 or its components in Windows

Important Internet Protocol version 6 (IPv6) is a mandatory part of Windows Vista and later versions of Windows. We do not recommend that you disable IPv6 or its components. If you do, some Windows components may not function. Additionally, system startup will be delayed for 5 seconds if IPv6 is disabled by incorrectly, setting the DisabledComponents registry setting to a value of 0xfffffff. The correct value should be 0xff. For more information, see the „What are Microsoft’s recommendations about disabling IPv6?“ question in IPv6 for Microsoft Windows: Frequently Asked Questions.
Manually disable or re-enable IPv6 or its components

Disable IPv6

You can disable IPv6 on the host computer through the DisabledComponents registry value. The DisabledComponents registry value affects all network interfaces on the host.

Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

To disable certain IPv6 components, follow these steps:

  1. Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list.
  2. In the User Account Control dialog box, click Continue.
  3. In Registry Editor, locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
  4. Double-click DisabledComponents to change the DisabledComponents entry.Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:
    1. In the Edit menu, point to New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents, and then press Enter.
    3. Double-click DisabledComponents.
  5. Type any of the following values in the Value data field to configure the IPv6 protocol to the intended state, and then click OK:
    1. Type 0 to re-enable all IPv6 components (Windows default setting).
    2. Type 0xff to disable all IPv6 components except the IPv6 loopback interface. This value also configures Windows to prefer using IPv4 over IPv6 by changing entries in the prefix policy table. For more information, see Source and destination address selection.
    3. Type 0x20 to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
    4. Type 0x10 to disable IPv6 on all nontunnel interfaces (both LAN and Point-to-Point Protocol [PPP] interfaces).
    5. Type 0x01 to disable IPv6 on all tunnel interfaces. These include Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), 6to4, and Teredo.
    6. Type 0x11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

Use the DisabledComponents registry value to verify whether IPv6 is disabled. To do this, run the following command at a Windows command prompt:

reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents

When you do this, you may receive the following error message:

ERROR: The system was unable to find the specified registry key or value.

If you receive this error message, the DisabledComponents registry value is not set. If the DisabledComponents value is set, it overrides the settings in the connection properties.

Disable IPv6 on a specific network adapter

You can do this by unbinding the adapter in the Local Area Connection Properties dialog box:

  1. Click Start, and then click Control Panel.
  2. Click Network and Sharing Center.
  3. In the View your active networks area, click Local Area Connection, and then click Properties.
  4. On the Networking tab, clear the Internet Protocol Version 6 (TCP/IPv6) check box, and then click OK.

Note The Internet Protocol Version 6 (TCP/IPv6) check box affects only the specific network adapter and will unbind IPv6 from the selected network adapter. To disable IPv6 on the host, use the DisabledComponents registry value. The DisabledComponents registry value does not affect the state of the check box. Therefore, even if the DisabledComponents registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is expected behavior.

Prefer IPv6 over IPv4 in prefix policies

  1. Find the current value data of DisabledComponents.
  2. Change the data to binary data. It will be a 32-bit binary value.
  3. Find the sixth bit of the data, and then set it to 0. Do not change any other bits. For example, if the current data is 11111111111111111111111111111111, the new data should be 11111111111111111111111111011111.
  4. Change the data from binary to hexadecimal.
  5. Set the hexadecimal value as the new value data for DisabledComponents.

Re-enable IPv6 on all nontunnel interfaces

  1. Find the current value data of DisabledComponents.
  2. Change the data to binary data. It will be a 32-bit binary value.
  3. Find the fifth bit of the data, and then set it to 0. Do not change any other bits. For example, if the source data is 11111111111111111111111111111111, the new data should be 11111111111111111111111111101111.
  4. Change the data from binary to hexadecimal.
  5. Set the hexadecimal value as the new value data for DisabledComponents.

Re-enable IPv6 on all tunnel interfaces

  1. Find the current value data of DisabledComponents.
  2. Change the data to binary data. It will be a 32-bit binary value.
  3. Find the first bit of the data, and then set it to 0. Do not change any other bits. For example, if the source data is 11111111111111111111111111111111, the new data should be 11111111111111111111111111111110.
  4. Change the data from binary to hexadecimal.
  5. Set the hexadecimal value as the new value data for DisabledComponents.

Re-enable all IPv6 interfaces except for the IPv6 loopback interface

  1. Find the current value data of DisabledComponents.
  2. Change the data to binary data. It will be a 32-bit binary value.
  3. Find the first bit of the data and the fifth bit of the data, and then set them both to 0. Do not touch any other bits. For example, if current data is 11111111111111111111111111111111, the new data should be 11111111111111111111111111101110.
  4. Change the data from binary to hexadecimal.
  5. Set the hexadecimal value as the new value data for DisabledComponents.

Notes

  • Administrators must create an .admx file to expose the settings in step 5 in a Group Policy setting.
  • You must restart your computer for these changes to take effect.
  • value other than 0x0 or 0x20 causes the Routing and Remote Access service to fail after this change takes effect.
About the 6to4 tunneling protocol

By default, the 6to4 tunneling protocol is enabled in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 when an interface is assigned a public IPv4 address (that is, an IPv4 address that is not in the ranges 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). 6to4 automatically assigns an IPv6 address to the 6to4 tunneling interface for each such address that is assigned, and 6to4 will dynamically register these IPv6 addresses on the assigned DNS server. If this behavior is not desired, we recommend that you disable IPv6 tunnel interfaces on the affected hosts.

Written by Armin Senger

September 12th, 2016 at 2:42 pm

Posted in IT

Star Wars Identities

leave a comment

Ich war letztens in München um die Ausstellung „Star Wars Identities“ anzusehen. Die Exponate sind klasse, die soziologische Einbettung fand ich eher nicht so prickelnd. Habt Spaß mit den Fotos!

Written by Armin Senger

August 26th, 2016 at 2:58 pm

Posted in foto

Exchange Start – Stop via Batch

leave a comment

Quellen:
http://exchange.sembee.info/2010/shutdown-script.asp
http://kevin-olbrich.de/alle-exchange-2013-dienste-neu-starten-bat/

Exchange 2010 Server Shutdown Script

On This Page

  • Introduction – Why Use a Script to Shutdown Exchange?
  • Shutdown Script
  • What Does the Script Do?
  • Shutdown or Restart the Server After Stopping Exchange
  • Starting Exchange with a Script

Other Versions of Exchange

This article is available for other versions of Exchange:

Exchange 2003
Exchange 2007

Introduction – Why Use a Script to Shutdown Exchange?

If you are running Exchange 2010 on a domain controller, then you will find that it takes the machine a long time to shutdown. This is because the domain functionality stops quicker than Exchange, therefore Exchange is unable to write to the domain controller and has to be be „killed“ by the operating system.

This continual „killing“ of the Exchange services, instead of allowing them to shutdown gracefully is not good for the database and is one of the prime reasons for recommending that Exchange is not installed on a domain controller.

A better option is to stop the services before you begin to shutdown the server. This will also cause the server to shutdown more quickly because it isn’t waiting for the services to timeout. This can significantly decrease the shutdown/reboot time of SBS Server.

Even if you have a dedicated Exchange server, if you are using a UPS, then you may also want to shutdown the Exchange services before the UPS shuts down the OS. In many cases the domain controller may shut down before Exchange, which will cause delays as Exchange needs to communicate with the the domain controller during the shutdown process.

While you can stop the services yourself using the services administrative tool, instead use a batch script with a shortcut on the desktop.
Due to the dependencies required for some services, you can shortcut the list by stopping one service with the /y command.

Shutdown Script

Below is a sample script. Simply copy and paste it in to a new notepad document and save it as „stop-exchange.cmd“.

net stop msexchangeadtopology /y
net stop msexchangefba /y
net stop msftesql-exchange /y
net stop msexchangeis /y
net stop msexchangesa /y
net stop iisadmin /y
net stop w3svc /y

What does the script do?

net stop msexchangeadtopology /y

Stops the „Microsoft Exchange Active Directory Topology Service“ which will stop the following services

Microsoft Exchange Transport Log Search
Microsoft Exchange Transport
Microsoft Exchange Throttling
Microsoft Exchange Service Host
Microsoft Exchange Search Indexer
Microsoft Exchange RPC Client Access
Microsoft Exchange Replication
Microsoft Exchange Protected Service Host
Microsoft Exchange Mail Submission
Microsoft Exchange Mailbox Replication
Microsoft Exchange Mailbox Assistants
Microsoft Exchange File Distribution
Microsoft Exchange EdgeSync
Microsoft Exchange Anti-spam Update
Microsoft Exchange Address Book

It will also stop POP3, IMAP4 and Unified Messaging if those are enabled.

net stop msexchangefba /y

stops the „Microsoft Exchange Forms-Based Authentication“ service which does not have any dependencies

net stop msftesql-exchange /y

stops the „Microsoft Search (Exchange)“ service which does not have any dependencies

net stop msexchangeis /y

stops the „Microsoft Exchange Information Store“ service which does not have any dependencies

net stop msexchangesa /y

stops the „Microsoft Exchange System Attendant“ service which does not have any dependencies

net stop iisadmin /y

stops the IIS admin service, which does not have any dependencies.

net stop w3svc /y

stops the „World Wide Web Publishing“ service, which may have any dependencies – on SBS this will also stop the Remote Desktop Gateway service, which could kick you out of the server if you are using the RWW to access the server.

Shutdown or Restart the Server After Stopping Exchange

If you are using these scripts to shutdown Exchange before a server is shutdown (for example by a UPS) or rebooted, then you may want to fully automate the process by scripting the shutdown/restart as well. This can be easily achieved by adding an extra line to the end of the script:

Restart the server

shutdown /r /t 00

Shutdown the server

shutdown /s /t 00

Starting Exchange with a Script

Finally, you might also want a script to start Exchange again. This can be useful if you apply an update which requires a restart of the Exchange services, but don’t need to restart the server. However starting the services is a little more complex as the less number of the services are dependant on other services. Therefore more services have to be started manually. Simply copy and paste it in to a new notepad document and save it as „start-exchange.cmd“.

Remember to add POP3 and IMAP services if you are using those.

net start „World Wide Web Publishing Service“
net start „Microsoft Exchange System Attendant“
net start „Microsoft Search (Exchange)“
net start „Microsoft Exchange Information Store“
net start „Microsoft Exchange Unified Messaging“
net start „Microsoft Exchange Transport Log Search“
net start „Microsoft Exchange Transport“
net start „Microsoft Exchange Throttling“
net start „Microsoft Exchange Service Host“
net start „Microsoft Exchange Search Indexer“
net start „Microsoft Exchange RPC Client Access“
net start „Microsoft Exchange Replication“
net start „Microsoft Exchange Protected Service Host“
net start „Microsoft Exchange Mailbox Replication“
net start „Microsoft Exchange Mailbox Assistants“
net start „Microsoft Exchange Mail Submission“
net start „Microsoft Exchange Forms-Based Authentication service“
net start „Microsoft Exchange File Distribution“
net start „Microsoft Exchange EdgeSync“
net start „Microsoft Exchange Anti-spam Update“
net start „Microsoft Exchange Address Book“

Bemerkung: dieses Skript funkioniert nur mit der englischen Version. Umgearbeitet nach universell siehe anschließend: (Download meines Skripts ganz am Ende des Beitrags)

net start W3SVC
net start MSExchangeADTopology
net start MSExchangeEdgeSync
net start wsbexchange
net start MSExchangeAB
net start MSExchangeAntispamUpdate
net start MSExchangeFDS
net start MSExchangeServiceHost
net start MSExchangeThrottling
net start MSExchangeIS
net start MSExchangeMailSubmission
net start MSExchangeMailboxAssistants
net start MSExchangeMailboxReplication
net start MSExchangeRepl
net start MSExchangeRPC
net start MSExchangeSearch
net start MSExchangeSA
net start MSExchangeTransport
net start MSExchangeTransportLogSearch
net start msftesql-Exchange
net start MSExchangeMonitoring


Alle Exchange 2013-Dienste neu starten (Batch / PowerShell / .bat / .ps1)

By | September 24, 2014
 

Wer auf die Schnelle mal alle Exchange-Dienste neustarten möchte, der kann einfach folgendes in eine normale PowerShell-Konsole kopieren:

$services = Get-Service | ? { $_.name -like „MSExchange*“ -and $_.Status -eq „Running“}
foreach ($service in $services) {Restart-Service $service.name -Force}

Unter Umständen kommt eine Meldung wegen Timeout auf ausgelasteten Servern, diese kann einfach ignoriert werden.

Der Original-Beitrag:

Quick Tip: Restarting all Microsoft Exchange services

There are times when you need to restart all Exchange related services so here are 2 small scripts that will help you achieve this without going over each service in the Services mmc.

Of course restarting the “Microsoft Exchange Active Directory Topology” will restart a most of them but these 2 will restart them all.

Restarting All Running Services

This will get all services starting with MSexchange that are running and restart them.

$services = Get-Service | ? { $_.name -like „MSExchange*“ -and $_.Status -eq „Running“}

foreach ($service in $services) {Restart-Service $service.name -Force}

Restarting All Running Services with startup type Automatic

Although the above script should be enough in most cases, it will not restart any Microsoft Exchange related service that is supposed be running but is not for any reason. Here is another version of the script that would take care of this issue, note that we are looking for all services starting with MSExchange with startup type Automatic and restarting them

$services = get-wmiobject win32_service | ? {$_.name -like „MSExchange*“ -and $_.StartMode -eq „Auto“}

foreach ($service in $services) {Restart-Service $service.name -Force}

That’s it for now

via Quick Tip: Restarting all Microsoft Exchange services | zero hour sleep.

Mein Skript für Exchange 2010, Deutsch zum Download als Textfile.
Vor dem Einsatz bitte durcharbeiten und nach .cmd umbenennen. Ich übernehme keinerlei Haftung für eventuelle Schäden:

stop start exchange

Read the rest of this entry »

Written by Armin Senger

August 19th, 2016 at 9:42 am

Posted in IT

Step by Step : Installing & Configuring WSUS in Server 2012 R2

leave a comment

Quelle: https://mizitechinfo.wordpress.com/2013/08/19/step-by-step-installing-configuring-wsus-in-server-2012-r2/

Hier nur der Teil über die Verteilung via Gruppenrichtlinien:

22 – Next, let’s add Computer Group to WSUS, this method is to make sure that any computer listed in the Computer Group will get the Updates from WSUS Server…

On the WSUS console, click Options and then double click Computers

26

23 – In the Computers dialog box, select Use Group Policy or registry settings on computers then click OK…

** I choose Use Group Policy because I wanted all my Clients getting windows updates by GPO…

27

24 – Next, click All Computers, and then, in the Actions pane, click Add Computer Group…

28

25 – In the Add Computer Group dialog box, in the Name text box, type Comsystem Laptop, and then click Add…

29

26 – Once you successfully add a New Computer Group to WSUS, now we need tocreate new GPO and configure it so that all our clients will be effected by this GPO to get the Windows Updates…

** On the Domain Server, open Group Policy Management,  right click Comsystem Laptop and then click Create a GPO in this domain, and Link it here…

30

27 – In the New GPO dialog box, type WSUS Comsystem Laptop ,and then click OK…

31

28 – Next, right-click WSUS Comsystem Laptop, and then click Edit…

32

29 – Next, in the Group Policy Management Editor, under Computer Configuration, double-click Policies, double-click Administrative Templates, double-click Windows Components, and then click Windows Update…

33

30 – Next, in the Setting pane, double-click Configure Automatic Updates, and then click the Enabled option, under Options, in the Configure automatic updating field, click and select 3 – Auto download and notify for install, and then click OK…

34

31 – In the Setting pane, double-click Specify intranet Microsoft update service location, and then click the Enabled option, then in the Set the intranet update service for detecting updates and the Set the intranet statistics server text boxes, type http://dc01.comsys.local:8530, and then click OK…

35

32 – In the Setting pane, double click Enable client-side targeting, in the Enable client-side targeting dialog box, click the Enabled option, in the Target group name for this computer text box, type Comsystem Laptop, and then click OK…

36

33 – Next, let’s log in to our client PC as domain administrator and verify that our client is receiving the GPO by typing gpresult /r in the command prompt, In the output of the command, confirm that, under COMPUTER SETTINGS, WSUS Comsystem Laptop is listed under Applied Group Policy Objects…

37

34 – Next, we need to Initialize the Windows Update by typing Wuauclt.exe/reportnow /detectnow in the cmd…

38

35 – Next, we need to Approve and at the same time deploy an Update to our client PC…

in WSUS console, under Updates, click Critical Updates, right click any updates you prefer for your client PC and then click Approve…

40

36 – In the Approve Updates window, in the Comsystem Laptop drop-down list box, select Approved for Install…

41

37 – Next, Click OK and then click Close…

42

43

38 – Now, to deploy the selected updates, on the Client PC, in the cmd type Wuauclt.exe /detectnow…

44

39 – before you confirm the client can receive the update from the WSUS Server,return to WSUS Server and the on the WSUS console, on the Download Status, verify that the necessary / selected updates is finish downloading…

45

40 – Next, Click Critical Updates, an the right panes, verify that few updates is stated 100%…

46

41 – Now return to Client PC and open Windows Update from Control Panel, you should notice update available for your client PC and you can proceed with installation…

47

48

We done for now, please wait for my next post..:-)

Written by Armin Senger

August 17th, 2016 at 9:25 am

Posted in IT

WSUS auf Server 2012R2

leave a comment

Quelle: http://www.wsus.de/wsus_auf_w2012

HowTo > WSUS auf Windows Server 2012 installieren
WSUS auf Windows Server 2012 installieren

wsus_auf_w2012.pdf

Written by Armin Senger

August 17th, 2016 at 9:05 am

Posted in IT