Entering the GUID of the computer in Windows Server 2003įind the attribute named netbootGUID and edit it. The computer is shown as CN=ComputerName. Navigate to Domain -> DC=domain,DC=tld -> Container-or-OU-Name.
After installation go to Run and type adsiedit.msc. For this purpose you’ll have to install the ADSI editor. Our aim is to modify an attribute named netbootGUID of the computer object and enter the GUID of that computer. Modifying the netbootGUID attribute in Windows Server 2003 This is where steps differ between Windows 20. The next step is to enter the GUID of the computer. Enter the name of the computer which is to be prestaged This is the computer name which is displayed under the “Computer Name” tab of the system properties. Enter the netBIOS name of the computer you wish to prestage. This needn’t necessarily be the computers container it can be any OU. Right-click the container inside which you wish to place the computer, navigate to new -> computer. Go to Start – > Control Panel -> Administrative Tools -> Active Directory Users and Computers or Start -> Run and type dsa.msc. Entering the GUID is done differently on windows server 20 so the first step is to create a computer object which is same on all Windows Server editions. If your domain controller is also a WDS server you’ll have the option of entering the GUID of the computer while creating a computer object, but otherwise there is no “direct” option to enter the GUID.
By default if you join a computer to a domain the computer object is created in the Computers container, even though you can move it to another container later, by prestaging you can place the computer inside the container of your choice even before joining it to the domain. By prestaging a computer you can make sure the WDS (Windows Deployment Services) server responds only to known computers. Prestaging means to add a computer to the Active Directory database before joining the computer to the domain.
This tutorial explains prestaging a computer object in the Windows Active Directory database.
0 kommentar(er)
