Mayjestic 12's webLOG » Scripting http://12.mayjestic.net "If madness becomes business - lunatic's becomes professionals" Mon, 14 Jun 2010 09:09:44 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Easily transfer FSMO Roles vom one DC to a another http://12.mayjestic.net/index.php/2007/12/12/easily-transfer-fsmo-roles-vom-one-dc-to-a-another/ http://12.mayjestic.net/index.php/2007/12/12/easily-transfer-fsmo-roles-vom-one-dc-to-a-another/#comments Wed, 12 Dec 2007 12:37:55 +0000 Roland http://12.mayjestic.net/index.php/2007/12/12/easily-transfer-fsmo-roles-vom-one-dc-to-a-another/ I’ve wrote a nice batch script how you can transfer FSMO Roles from one domaincontroller to a another. With some simple choices you can move roles between domaincontrollers in a AD environment.

Therefor i use the NTDSUTIL.EXE of the Windows Server Support Tools wich is installed by default on a Windows Domaincontroller.

Before you can use the script: Look if the path to NTDSUTIL.EXE is in the %PATH% variable, to call it globally. Or copy NTDSUTIL.EXE into the script directory. CHOICE.EXE is used to handle the choosable options in the script.

Script call: FSMOtransfer.bat [DNSDOMAIN]

Where [DNSDOMAIN] Must be a Fully Qualified Domain name (FQDN) of a existing Microsoft Active Directory Domain. The script works only if you are logged on as a administrator

Download: FSMORolesTransferScript

Happy Coding!

]]> http://12.mayjestic.net/index.php/2007/12/12/easily-transfer-fsmo-roles-vom-one-dc-to-a-another/feed/ 1 Fehlersuche/Troubleanalyse mit dem EventLog und seinen Tools http://12.mayjestic.net/index.php/2007/05/25/fehlersuchetroubleanalyse-mit-dem-eventlog-und-seinen-tools/ http://12.mayjestic.net/index.php/2007/05/25/fehlersuchetroubleanalyse-mit-dem-eventlog-und-seinen-tools/#comments Fri, 25 May 2007 10:56:14 +0000 Roland http://12.mayjestic.net/index.php/2007/05/25/fehlersuchetroubleanalyse-mit-dem-eventlog-und-seinen-tools/ Folgende Commandline-Tools sind zur Fehleranalyse unter Windows 2000 | XP | 2003 geeignet:

Das mit cscript startende VB-Script: EventQuery.vbs (ist beim Windows Server 2k3 im Resource Kit mit dabei) und WMIC.EXE (eine Schnittstelle der Windows Management Instrumentation, kann diesen Fehler auslesen auch vom lokalen System uns vom Remote Hosts)
WMI ist ein ‘Common Standard’ welcher immer mehr in den Vordergrund rückt. Bietet auch Schnittstellen für VB, C, .NET….

Hier ein kleines Beispiel, was WMIC so alles kann:

wmic /NODE:”%computername%” NTEVENT GET Message

Auch Ausgaben in HTML sind bei manchen Schaltern moeglich!

]]> http://12.mayjestic.net/index.php/2007/05/25/fehlersuchetroubleanalyse-mit-dem-eventlog-und-seinen-tools/feed/ 0