Not surprising at all. PXE reports the contents of the UUID array, while
Win32_ComputerSystemProduct contains the Windows GUID.

 

Here is how it maps:

 

#

# guidstr

#

# takes a 16-byte array and turns it into the standard

# text guid format.

#

# try as i might, i couldn't get system.guid in .net

# to work.

#

# 3,2,1,0

# 5,4

# 7,6

# 8,9

# 10,11,12,13,14,15

#

function guidstr([byte[]]$b)

{

                if ($b.length -ne 16)

                {

                                return "";

                }

 

                $f = "{0:x2}";

                $str  = ($f -f $b[3]) + ($f -f $b[2]) + ($f -f $b[1]) + ($f
-f $b[0]);

                $str += "-";

                $str += ($f -f $b[5]) + ($f -f $b[4]);

                $str += "-";

                $str += ($f -f $b[7]) + ($f -f $b[6]); 

                $str += "-";

                $str += ($f -f $b[8]) + ($f -f $b[9]); 

                $str += "-";

                $str += ($f -f $b[10]) + ($f -f $b[11]); 

                $str += ($f -f $b[12]) + ($f -f $b[13]); 

                $str += ($f -f $b[14]) + ($f -f $b[15]); 

 

                return $str;

}

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 24, 2008 2:41 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

Here's a real mind screw:

Win32_ComputerSystemProduct has a UUID which suggests on one PC:

54674461-7948-1000-9A34-000E0C6A5779

When it boots, the PXE code says:

61446754-4879-0010-9A34-000E0C6A5779

 

Notice the first 3 groups are the same numbers, but just mixed up?

 

What is that all about?

 

Thanks!
jlc

 

From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 24, 2008 11:57 AM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

Hey Michael,

I am using CIM Studio to look for this, and call me dense but I can't find
it J
Can you push me along a bit here?

 

Thanks!
jlc

 

From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 4:45 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

The SMBIOS GUID. Which is properly a CIM UUID (and that's what SCCM calls
it).

 

RIS/WDS doesn't care about the objectGUID. That's a crappy error message.

 

It's pretty easy to scan through AD using vbscript or PS and retrieve all
the UUIDs with WMI.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 6:38 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

So when a cheap mobo has a dupe guid with another, which guid in AD does RIS
say "A GUID for this computer already exists in Active Directory."?
Any idea?

Thanks!
jlc

 

From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 4:28 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

The SMBIOS GUID used by WDS is tied to the motherboard, not to the AD
object. Sorry, I didn't know that that was what you were looking for.

 

You get that from WMI (for compliant motherboards). For example:

 

PS C:\Users\Michael> gwmi win32_computersystemproduct | fl uuid

 

uuid : 61383066-3835-3962-6635-001B384EE42B

 

PS C:\Users\Michael>

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 1:57 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

Hey Michael,

Am I missing something here? I thought machine's deployed via WDS/RIS used
the GUID as reported by the wkst?
During the post I can see them and they are very different from the guid's
enumerated by adfind. I have not blacklisted any guids yet, and none of them
correspond to the mac address that I can visual see which would be a result.
The deployments were CD based, not image based.

 

Any ideas?

 

Thanks!
jlc

 

From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 15, 2008 4:32 PM
To: NT System Admin Issues
Subject: RE: Enumerate GUIDs for all comps in an OU

 

Adfind -default -b ou=ouname -f name=* objectGuid

 

?

 

If you actually want vbscript for it, I can hunt it down. But it's a LOT
more lines.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 15, 2008 6:23 PM
To: NT System Admin Issues
Subject: Enumerate GUIDs for all comps in an OU

 

Anyone know a query I can do through vb for this?

 

Thanks!
jlc

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to