Re: Cleaning up Duplicate GUIDS

From: Shawn Stewart (shawn.stewart_at_absg.com)
Date: 12/08/04


Date: Wed, 8 Dec 2004 13:12:46 -0600

Create a collection of machines with duplicate guids.
Advertise newuid.exe /s /allocate to the collection. (Make sure you set the
program to run only when a user is logged on for use with /allocate.
Otherwise, you can orphan your client.)
Let this advertisement clean up your dups, and you should be okay for
upgrading to SMS 2003.

Shawn

"Judd" <Judd@discussions.microsoft.com> wrote in message
news:E5A7B53A-DB46-4B15-B4D8-559D77632569@microsoft.com...
> Before we upgrade to 2003 I need to clean up all duplicate guid's. The
> problem that I am having is setting up the package to execute the
newuid.exe
> /s /allocate.
> I need a script to either run it from a package on a server or copy it
local
> to a machine then run it.
> I don't have a problem with cleaning the database it's fixing the clients
> are the problem so it doesn't keep coming back.
> What is the best approach? Doesn't anyone already have a script/ package
> written to do this?



Relevant Pages

  • Re: duplicate computer names in SMS2003
    ... Is there a way to get rid of duplicate Guids? ... machines or statis DNS entries and I need to correct this in order to ... > Is it duplicate Discovery information or duplicate GUIDs? ...
    (microsoft.public.sms.setup)
  • Re: Idea for a business... not entirely OT.
    ... machines then why not try offering that as a service. ... Don't advertise ... the library or adult education courses - and the rest won't want to pay. ...
    (uk.comp.sys.mac)
  • Re: IPSec Security
    ... for machines on the 172 side ... reg keys so that they do not advertise their presence. ...
    (microsoft.public.win2000.security)