aparis99

Windows 7 machines had CD Keys, Win8/10 don't since they're 'embedded'. My understanding is that they have a full key or partial key and when you activate after an upgrade, it generates a unique key for Microsoft's database with your hardware and you're good to go with a clean install or whatever in the future. We have about 75 machines that have Win8/10 licenses, but came from Dell with Win7 installed. All of our OS licenses are OEM. We've been upgrading some with the CD from Dell, another handful with a USB Key via the Media Creation Tool (build 10586), and finally imported an SCCM Task Sequence from Microsoft for an In Place Upgrade (build 10240). That works great, but come to find out none of them are activating! When looking at them, we see they've all got the same Win10 generic key ending in T83GX, and of course activation gives a "DNS error". Can anyone explain what's going on here? Am assuming this SCCM upgrade has this generic key embedded somewhere and not pulling the info from the OS it's being installed on...

Try this start-> Run--> c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -iru

In case anyone wants to know, I figured it out. Solution: You can configure the AD System Discovery agent to include the attribute for the Location and then use it in queries.

We have a Computers OU setup in AD, with sub-OU's by department, then again into Desktops and Laptops. This helps when pushing something to a department, but I've setup Windows Updates to hit at different times depending on building locations. (ex: Our IT dept is spread across 2 buildings). I want to setup a query to make a collection depending on which building they are in. Is it possible to use this AD location to make a dynamic query?

Thanks, that's what I figured. Well, if we start with a fresh version of 2012 and take down the 2007 server, that wouldn't be an issue would it? Would there be any good way of migrating windows update settings and Forefront administration or would that have to be setup from scratch too? Trying to figure out which would be more trouble, rebuilding the 2012 environment, or starting fresh.

OK, I took out the boundaries, so now can I do anything about the Site Code being the same? They are both the same.

Background: We have 1 SCCM 2007 server. We are a small 250 computer company and this one server houses the SQL database, DP, MP etc all in one. The only thing that our 2007 server is doing is Forefront management and updates, and windows updates. It was partially setup over time with various people and so we want to setup the new server and start fresh. (Migrating only Windows updates and Forefront settings would help) I think we've messed up something. The 2007 is in production, and we followed the 2012 setup pages on here. (We are on part 5) It was brought to our attention that a few of the computers' Configuration Manager Properties were showing their Management Point was the new server. Is this cause for concern? Also, we were going to see about setting up the migration source hierarchy and it shows "Failed (Duplicated site code with current hierarchy)". I thought we made sure it was different so how to I check each server's site code? If they are the same, do we need to rebulid the new environment? We started out pretty confident... not so much now (If anyone is available for IM'ing, that'd be cool)