Es kann ja mal vorkommen, dass man den WSUS Content (Patches, Service Packs,…) auf ein anderes Drive verschieben muss. Dafür gibts ein Tool, d.h. “wsusutil”.
Dies ist im Tools Ordner der WSUS Installation. Die Syntax lautet wie folgt:
C:\Program Files\Update Services\Tools>wsusutil movecontent D:\OrdnerXyz
written by repa
der Titel war eine meiner Aufgaben heute. Dazu gibts auch einen MS Artikel. Bei mir ging der Restore jedoch nur, wenn ich die Registry nicht importiert habe!
| 1. |
Note the certificate templates that are configured in the Certificate Templates folder in the Certification Authority snap-in. The Certificate Templates settings are stored in Active Directory. They are not automatically backed up. You must manually configure the Certificate Templates settings on the new CA to maintain the same set of templates.
Note The Certificate Templates folder exists only on an enterprise CA. Stand-alone CAs do not use certificate templates. Therefore, this step does not apply to a stand-alone CA. |
| 2. |
Use the Certification Authority snap-in to back up the CA database and private key. To do this, follow these steps:
| a. |
In the Certification Authority snap-in, right-click the CA name, click All Tasks, and then click Back up CA to start the Certification Authority Backup Wizard. |
| b. |
Click Next, and then click Private key and CA certificate. |
| c. |
Click Certificate database and certificate database log. |
| d. |
Use an empty folder as the backup location. Make sure that the backup folder can be accessed by the new server. |
| e. |
Click Next. If the specified backup folder does not exist, the Certification Authority Backup Wizard creates it. |
| f. |
Type and then confirm a password for the CA private key backup file. |
| g. |
Click Next, and then verify the backup settings. The following settings should be displayed:
| • |
Private Key and CA Certificate |
| • |
Issued Log and Pending Requests |
|
| h. |
Click Finish. |
|
| 3. |
Save the registry settings for this CA. To do this, follow these steps:
| a. |
Click Start, click Run, type regedit in the Open box, and then click OK. |
| b. |
Locate and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration
|
| c. |
Click Export. |
| d. |
Save the registry file in the CA backup folder that you defined in step 2d. |
|
| 4. |
Remove Certificate Services from the old server. |
| 5. |
Rename the old server, or permanently disconnect it from the network. |
| 6. |
Install Certificate Services on the new server. To do this, follow these steps.
Note The new server must have the same computer name as the old server.
| a. |
In Control Panel, double-click Add or Remove Programs. |
| b. |
Click Add/Remove Windows Components, click Certificate Services in the Windows Components Wizard, and then click Next. |
| c. |
In the CA Type dialog box, click the appropriate CA type. |
| d. |
Click Use custom settings to generate the key pair and CA certificate, and then click Next. |
| e. |
Click Import, type the path of the .P12 file in the backup folder, type the password that you chose in step 2f, and then click OK. |
| f. |
In the Public and Private Key Pair dialog box, verify that Use existing keys is checked. |
| g. |
Click Next two times. |
| h. |
Accept the Certificate Database Settings default settings, click Next, and then click Finish to complete the Certificate Services installation. |
|
| 7. |
Stop the Certificate Services service. |
| 8. |
Locate the registry file that you saved in step 3, and then double-click it to import the registry settings. If the path that is shown in the registry export from the old CA differs from the new path, you must adjust your registry export accordingly. By default, the new path is C:\Windows in Windows Server 2003. |
| 9. |
Use the Certification Authority snap-in to restore the CA database. To do this, follow these steps:
| a. |
In the Certification Authority snap-in, right-click the CA name, click All Tasks, and then click Restore CA.
The Certification Authority Restore Wizard starts. |
| b. |
Click Next, and then click Private key and CA certificate. |
| c. |
Click Certificate database and certificate database log. |
| d. |
Type the backup folder location, and then click Next. |
| e. |
Verify the backup settings. The Issued Log and Pending Requests settings should be displayed. |
| f. |
Click Finish, and then click Yes to restart Certificate Services when the CA database is restored. |
|
| 10. |
In the Certification Authority snap-in, manually add or remove certificate templates to duplicate the Certificate Templates settings that you noted in step 1. |
written by repa
Heute morgen begrüsste mich die folgende Meldung auf einem Windows Server 2003 mit Citrix 4.5 FR 1 installiert:
MMC cannot open Snap-in Name. This may be because the file does not exist, is not an MMC console, or was created with a later version of MMC. This may also be because you do not have sufficient access rights to the file.
Der Server wurde am vorhergehenden Tag installiert und konfiguriert und lief eigentlich ohne Probleme – vor allem alle MMC Snapins liefen ohne Probleme.
Nunja, warum dieser Fehler jetzt auftaucht ist schleierhaft, ausser dem Virenscanner und Citrix ist nichts auf dem Server, hmm.
Nach einiger Zeit fand ich die Lösung. Mit dem Befehl
regsvr32 msxml3.dll
liefen alle MMC Snapins ohne Probleme.
written by repa
Bei Windows Server 2008 gibt es zwei versch. Installationsmöglichkeiten, mit oder ohne GUI.
Für die Variante ohne GUI (Core) hat Guy Teverovsky nun eine GUI entwickelt 
Features:
- Product Activation
- Configuration of display resolution
- Clock and time zone configuration
- Remote Desktop configuration
- Management of local user accounts (creation, deletion, group membership, passwords)
- Firewall configuration
- WinRM configuration
- IP configuration
- Computer name and domain/workgroup membership
- Installation of Server Core features/roles
Download & weitere Informationen…
written by repa
Falls in der DHCP MMC SnapIn noch alte “authorized” DHCP Server zu finden sind, können die wie folgt entfernt werden:
netsh dhcp delete server example.domain.local 10.10.10.10
Um einen DHCP via Command Line hinzuzufügen, kann der folgende Befehl verwendet
werden.
weiterlesen… »
written by repa
Das Problem mit SVCHOST.exe kennt jeder, es gibt viele Prozesse davon im Taskmanager, aber was dahinter steckt, ist auf den ersten Blick nicht ersichtlich.
Um dies herauszufinden gibt man in der CMD folgenden Befehl ein.
tasklist /svc
Nun kann der Task aufgrund der Process-ID, welche im Taskmanager ersichtlich ist, identifiziert werden.
z.B.:
svchost.exe 1580 TapiSrv
written by repa
microsoft hat longhorn server build 6001 an die tester rausgegeben.
ich habe mir das ganze angeschaut und auch einige screens gemacht.
die bilder sind in der gallery unter “Microsoft” “Longhorn Server 6001″ zu finden.
written by repa
