CM12 - Day 5 in the lab

Day 5

This lab just isn't intended to match production. So what I'm going to do for WSUS is use CM2's DB. CM2 is the primary site with SQL on it already. CM3 would be a SUP and have to call back to CM2 to do SUP queries. What this means now is that CM3$ wouldn't just be a logon with the MP role, but it'd have to be sysadmin so that it could create and own the SUSDB on CM2. That's fine in this lab scenario.

Also installing WSUS to its own web site on 8530.

So I go to make CM3 a SUP and it's not offered as a role. I figure I have to install the WSUS console on CM1 to get it to show as an option. No dice. Still won't offer it as a role that I can install. What gives? Ah, read whe SUPSetup.log - it wants .NET 4.0. All site role servers need it. Duh. Installed, but no dice. Remove\add the SUP role. Working now. Finally. So if you get the same error as shown in KB962224 the fix is almost certainly to install .NET 4.0.

Day 6

Since Software Updates is now syncing fine and since my clitest worked OK, it seems the next logical thing to do is try to migrate things off CM07. Do I need to migrate clients first? Where's the migration doc? Barf, the doc on Connect is for Beta 1. I'll go try the MMS Lab. I know there is a lab for migration there. Might as well get off on the right foot.

Oh crap. I should do SRS next so that I can watch the migration progress. Plus if I deploy software updates, I'll want to see the status. CM3 is supposed to be the catch-all, but CM4 could do it too since it's attached to CM1. Technically, it's rare to have lots of lower level SRS. But from another point of view, primary sites get lots of data - but just not enough for full reporting. Like ChildSite A would never have B's inventory data, but the CAS could if we shoot it up. Now, since SRS doesn't require IIS, I wonder if I should save time and just install SRS to CM1. Or should I bother to go install it to CM3...

Installing SRS, but now I wish I had just done this first so that I'd have local SQL for WSUS. Not because it's a load issue or anything, but just to better mirror production. Choosing to run it as system and that could help when it needs to query CM1. It has a logon over there already for WSUS, so now whatever perms it needs for SRS should be easier to setup.

Day 7

So guess what? My DP on my old CM7 site is gone. Why? I assume because I upgraded the DP without reading what that would mean. So on my CM07 site, I had to add that role back on to patch CM07 systems (and the CM07 primary itself) today. And on CM3, I just added a DP role since I intend to kill off the old DP entirely. It's a goofy 16 GB box with only 100 GB drive space. What good is that? It was a Dell loaner that we got for cheap, but I'll have to figure out a better use for it. Maybe just a tool box server (a server that the team can all logon to instead of logging on to the primary all the time). I have such a server now, but it's a VM that just eats disk space. And with the new backup in 2008 & R2 that backs up as a VHD, it'd be easy to restore to my old CM07 DP and go V to P.

Oh cool thought. With DP groups, you don't have to go park all your packages on a new DP. So I'll go see if my CliTest package is parked automatically. Don't like that? Think it could melt your line? Remember DPs now have a sender so you can throttle them if needed!