About 10,000 clients. very high turnover with the same name.(about 3000 machines are re-imaged and brought back with the same name) Understand Default SCCM Site properties Advanced tab setting of"Automatically create new client records for duplicate hardware IDs" will take care of this. Need to get HINV/SINV before machines are shipped out.What would be the best way to handle this scenario? Planning to prestage SCCM client so inventory is done before machine is shipped out.Also planning for PKI so can manage Internet based clients and NAP.Any thoughts?ThanksDilip

Consider the following Rule: You are deploying operating systems, such as Windows Vista or Windows Server 2008, to a large number of computers. You use a Windows Setup program to generate random computer names for these computers. In this scenario, duplicate IT computer names may be generated. Computers that have duplicate names cannot join the network or access network resources. You have to redeploy the operating systems to these affected computers.