I've been fussing around and suspect there is some issue with 64bit RSAT. Running 2k8R1 DC's and admining with Win7 desktops. With 64bit Win7, adding a new computer object to an OU leaves me only "OK" after adding initial name for PC. No "Next" which would then allow me to populate GUID info. When the same admin host was 32bit, this wasn't an issue. I've been scouring around looking for some description that matches this problem and can't find one. I see folks using OAC having issues. Thanks, Joe It appears I'm mistaken. I just fresh loaded a 32bit Win7 installation; the same issue exists. Anyone have *any* ideas here, this is odd... Bah! I'm going insane. I've reloaded boxes in various configurations (no applied group policy--no software policy, etc) and installed both 32 and 64 bit Win7 with the corresponding RSAT packages, then installed AD-DS-SnapIns and I *still* cannot pre-stage a host and put it's GUID in. On the Create Computer dialogue I only have Cancel/Ok/Help and no Cancel/Next to take me to the next step where a GUID would be entered.

So, There seems to be some indication that this is a feature and not a bug. I'm uncertain *why* it worked at some point in Win7, and doesn't now. I found some technet forums posting indicating that the GUID settings area *only* exist when WDS is installed, and that means it has to be an a 2k8 host. Seems a bit silly that we can't manage fully from our tech hosts. It makes documentation a bit annoying. http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/11207062-2db7-43f2-8eae-ca767a600c39 There are workarounds (ugly nasty ones). Can anyone *really* confirm that this shouldn't be available from a Win7 management host? It's more academic at this point anyway, as I only noticed it had changed when I was wanting to verify the modifications made by some scripts to the netbootGUID in AD using MMC. Thanks, J