ManicMailman

- DB server brought back up - External MP brought back up - WSUS server brought up Console works, reports work, clients are checking in verified by dates on device objects in SCCM console - All DPs brought back up - Deployed new software, works fine - Distributed content to DPs, works fine - "All Status Messages" Query found in Monitoring > System Status > Status Message Queries looks just like it did before P2V I think we're good, but if anyone has any recommendations of what to check which could be a "sleeper" problem, please feel free to share! I think the fact that the DB was on a separate server made this much simpler. Have a good one.

P2V has completed (VMware standalone converter installed on physical server). As I suspected, Windows is recognizing the new disks as unique from their originals. - Swapped a few drive letters around. - Verified Windows shares still function as before - Verified NTFS permissions on contents of "new" data drive hasn't changed. New VM snapshotted. Next step is to bring up DB server and do a little testing. Until then...

Howdy! Well, it looks like people either haven't done this before themselves or, perhaps, have tried and don't want to touch this post with a 10 ft pole. Or, maybe this should be in a VMWare forum... In any case, get your popcorn, we are currently at Step 6, beginning the Offline P2V process. I added the step of grabbing all NTFS and Share permissions on the machine prior to beginning the process because, again, I'm concerned that those may be lost and need to be recreated. I'll do my best to update the post with progress for those who find themselves in this position in the future.

Hey All, We are preparing to offline P2V our Primary Site server (have a plan in place, the only server in hierarchy that is physical) and are just looking for some insight from anyone who may been down this road before; offline P2V vs online P2V, pitfalls, etc. The entire hierarchy: 1 Primary Site server at central office (to be P2Ved) 1 DB server at central office 1 Management/Enrollment/Distribution point in DMZ for internet facing devices at central office 1 integrated WSUS server at central office 1 DP at central office 10 DPs at 10 different locations around town ~7000 managed devices Primary Site Server: C: Where the main bits are installed. (No SMS on drive file in place) D: Both SCCM's gold SCCMContentLib folder as well as the shared \\siteserver\sources "Sources" share are here (the thing that'll take the most time to vmdk) (500GB or so) The plan in chronological order: 0) Get a full SQL DB backup 0a)Check our SCCM site backups too (we weave both SQL and SCCM backups throughout the week) 1) Shutdown physical Primary Site Server 2) Shutdown DB server 3) Shutdown WSUS server 4) Shutdown Management/Enrollment/Distribution point in DMZ at central office 5) Shutdown the 10 remaining DPs located around town 6) P2V the Primary Site Server. I'm hoping the systems dudes are able to bring up the new VM with the D: drive already seen by Windows, but I'm not sure that's possible. They'll likely have to go into disk management to bring online and assign drive letter D: and then recreate the \\siteserver\sources share (I don't wan to have to modify all of our applications to point to a new UNC for source content) 7) Bring the VMed Primary Site Server up and make likely needed drive tweaks as quickly as possible. Verify D: drive contentlib folder and sources share. 8) Bring DB server up. 9) Bring Management/Enrollment/Distribution point in DMZ back up. 10)Bring WSUS server back up 11)Bring up DP at central office 12)Bring up the 10 remaining DPs that are around town 13)Prepare for the 2012 R2 to 2012 R2 SP1 upgrade with some peace of mind. Thanks in advance for any insight. I'm mostly concerned about SCCM's access to its gold SCCMContentLib and the availability of the sources UNC that every single one of my 133 apps is using post the offline P2V process. (Don't want to confuse SCCM's little brain and/or cause some kind of DB corruption.) _G