Fletcher's Cloud Blog

I can now post this, as my steps have been published on the SCSM Team Engineering site here.

Have you ever needed to build a pre-production environment to test an update or work on workflows, I did.

Thought I would share this and maybe it would help someone else as well.

It at the moment consists of the following.

1 Domain Controller

1 Management Server

1 Data Warehouse Server

So the steps I followed to create this.

1. Promote a new DC into Production, wait for replication.

2. Add a admin account to Schema Admins (this is needed later on) – Gotcha ONE

3. Do not reset any passwords of any run as accounts (learnt this one the hard way) – Gotcha TWO

4. Move DC into ring-fenced network.

5. Seize all required roles to the “Lab DC” (ntdsutil, this is where the Schema admin is needed for Schema Master)

2 GREAT resources from Petri (www.petri.co.il), if you administer Active Directory, you know this website

Delete Failed DCs from Active Directory

Seizing FSMO Roles

6. Restored a DPM backup of MS vhd and DW vhd

7. Restored the required databases for the MS (serviceManager LDF and MDF)

8. Restored the required databases for the DW (DataMart, StagingAndConfig and Repository)

9. Create the required Virtual Machines using the vhd’s you restored.

10. Present additional VHDs to replicate production drives. Each of the servers had two additional drives for MDF and LDF files respectively.

11. Copy the required MDF and LDF to the necessary locations on both the MS and the DW.

12. You may get an error in the Application Log of your SCSM MS Server regarding the creation of a log file. The first hint that there is a problem is that the service will start and then stop a few seconds later. I had to create the folder structure manually for the creation of the templog.ldf file – Gotcha THREE

13. Restart both MS and DW

14. Once restarted, check the System Center Data Access Service, System Center Management and System Center Management Configuration Services

15. Check for a warning regarding SPN, stating that a SPN must be created. – Gotcha FOUR

a. Log onto the server complaining about SPN (Usually MS and DW)

b. Run the following command (without quotes)

• i. “setspn –U domain\username –A MSOMSdksvc/netbiosnameofMS”
• ii. “setspn –U domain\username –A MSOMSdksvc/FQDNofMS”
• iii. “setspn –U domain\username –A MSOMSdksvc/netbiosnameofDW”
• iv. “setspn –U domain\username –A MSOMSdksvc/FQDNofMS”
• For example mine – “setspn –U europcar\sa-servicemanager -A MSOMSdksvc/SCSM
• For example mine – “setspn –U europcar\sa-servicemanager -A MSOMSdksvc/SCSM.servicemanager.demo

16. If you got the error mentioned above, restart  System Center Data Access Service, System Center Management and System Center Management Configuration Services

17. That got me up and running.