UPromoteMore InformationUPromote : Promote your NT Server to a Domain ControllerUPromote is the only software utility that can promote your NT server to an NT domain controller without re-installing the operating system. Don't make the wrong choiceWhen you installed Windows NT Server, you were asked if you wanted to create a a domain controller (DC). Your choice was permanent. If you declined, you could never create one later (Q193219). With UPromote you can:
What is a Domain Controller?A domain controller puts all of your passwords in a central database. When a user logs on to a desktop PC, it consults the domain controller to verify your password. A small organisation starts with a workgroup, a collection of machines that can share files and a printer. A domain is a larger collection of computers where access to files and printers is controlled by the domain controller. A domain has exactly one primary domain controller and optionally one or more backup domain controllers. Don't get bittenOnly UPromote can rescue you from a difficult dilemma: You need a DC but you already installed Windows NT Server without it. What do you do? Do you waste days of downtime while you re-install everything, or do you spend thousands of dollars on another computer? How It WorksUPromote works by updating the system registry. To create a PDC it converts all local user accounts to global user accounts. To create a BDC it copies the user accounts from the PDC and then synchronizes the Security Identifier (SID) to match the PDC. To create a standalone server it converts all global user accounts to local user accounts. It does not modify any EXE or DLL files. For technical details see UPromote Operation. Safe to UseUPromote has been thoroughly tested and is safe to use. The result is indistinguishable from a domain controller created using the Microsoft setup procedure. As an added precaution, it backs up your entire registry. This allows for easy recovery. Any domain controller created with UPromote can be safely upgraded to Windows 2000 Server. UPromote has been used to promote/demote NT servers at hundreds of businesses and colleges, including many Fortune 500 companies. See our list of satisfied users. Benefits
For More InformationFor more information, see the list of Frequently Asked Questions FAQWindows Server 2000 and 2003Q: Does UPromote run on Windows Server 2000 or Windows Server 2003? A: Windows Server 2000 and Windows Server 2003 use a radically different method for domain control called Active Directory (AD). AD is based on the Lightweight Directory Application Protocol (LDAP), which in turn is based on a subset of the international OSI X.500 standards for directory search and management. AD requires that you install the Domain Name System (DNS) and maintain directory trees for all machines in your organisation. Windows Server 2000 and 2003 have a built-in utility, DCPROMO.EXE, that will install Active Directory on your standalone server and promote it to a domain controller. NT 4 does not support AD directly. If your Windows 2000/2003 domain controller is running in pre-Windows 2000 compatibility mode ("mixed" mode), you can use UPromote to create an NT 4 DC that can join the Active Directory domain as a Backup Domain Controller (BDC). UPromote does not otherwise support Windows 2000/2003 Active Directory. Q: Can I use UPromote to demote a Windows NT 4.0 BDC from an Active Directory domain? A: Yes. You can use UPromote to remove your remaining NT domain controllers from your AD domain. Run UPromote and select "standalone server". After you are finished, go to "Active Directory Users & Computers" and delete the BDC from the folder "Domain Controllers". In some cases you may need to also delete it from "Active Directory Sites & Services" (Q216364). Afterwards you can join the computer to the domain as a member computer. Create the member computer object in the AD folder "Computers". (Check the box "Allow pre-Windows 2000 computers to use this account".) On the NT computer run the Control Panel Networking applet to join the computer to the domain. Server ManagerQ: Shortly after I promoted/demoted my server, I ran Server Manager (SRVMGR.EXE) on another computer. It reports that my server has not changed. Is something wrong? A: This is normal. It can take up to 60 minutes for Server Manager to notice the change. Exit and rerun SRVMGR.EXE and it will eventually correct itself. For technical details see The Network Neighborhood. Security IdentifiersQ: When I run UPromote to create a Backup Domain Controller (BDC), the program asks for permission to change the security identifier (SID) of my computer. What is a Security Identifier? A: A security identifier is a number that uniquely identifies a computer in a network. Each member computer in a domain has a unique SID. Windows networking requires that all the domain controllers in a domain must share the same SID. So when you add the BDC, its SID must be changed to match the PDC. Q: Why does every domain need a unique SID? A: The SID uniquely identifies a domain on the network. If two or more domains share the same SID, the member machines will appear to belong to both domains simultaneously. It is very important that each domain have a unique SID. If you are using the DC on an isolated network (e.g., for testing or training), you do not need to change the SID. Q: When UPromote changes the SID, it takes several minutes. What is it doing? A: To change the SID, UPromote scans your entire registry and all of your files. It changes the registry keys and the ownership of the files to use the new SID. Q: I heard I can move a BDC by using a SID-changing tool such as newsid or Symantec Ghost. Will this work? A: No. While SID-changing tools may work fine for NT Workstation, they do not work for NT Server. Changing the SID is necessary but not sufficient to move a BDC. For example, the database serial number must be synchronized with the PDC. Otherwise password replication will fail. UPromote will update all necessary registry values, in addition to changing the SID. Q: Why does UPromote ask to change the SID when it converts a DC back to a standalone machine? A: If you convert a domain controller back to a standalone machine, UPromote must change the SID to avoid a clash with the remaining domain controllers. The only time you do not need to change the SID is if you are destroying the domain; i.e., you know for certain that no other DCs exist and that no member computers belong to the domain. During testing, for example. Moving Between DomainsQ: I promoted a computer that was not originally a member of the domain. Will any applications be affected? A: If you join a new domain (or are creating a new domain), you may need to update the embedded domain name(s) in some applications.
Q: Can I use UPromote to move a BDC from one domain to another? A: Yes. You need to run UPromote twice. Run it the first time to demote the BDC to a standalone server. Then run it the second time to promote the standalone server to a BDC in the new domain. Note: A SID-changing tool such as newsid, and Symantec Ghost will change only the SID. Some web sites have claimed (e.g., the John Savill NT FAQ sites) that by changing only the SID you can move a BDC to another domain. This is not true. UPromote updates several additional registry keys which are essential in order to move a BDC from one domain to another safely and reliably. These registry keys include the password database serial number and the password database timestamp. Q: What happened to my old user accounts? Can I move user accounts between domains? A: When you move a BDC, its user accounts will be overwritten by the user accounts from the new PDC. If you need to preserve the old user accounts, you can use tools such as the Domain Migration Wizard from Aelita or the FastLane DM Consolidator from Quest Software to copy the user accounts to the new domain. Afterwards you can use UPromote to move the computer to the new domain as a BDC. Rejoining the Same DomainQ: I want to demote a BDC and rejoin it back to the same domain as a member server. Are there any special steps required? A: If your computer provides shared disks, you will probably want to preserve the ownership of the shared files on those disks so that your domain users can continue to access them. For all disks that offer shared files, select "Do not change these disks" on the UPromote SID ownership panel. This will preserve the domain SIDs in the ACLs of those files. For technical details see Changing the Security ID on Disks. After you rejoin the domain, run EXPLORER.EXE and re-add your domain groups to the share-level permission list of your shared folders and shared printers so that your domain users can continue to access them. For technical details see Security IDs and the Registry. When you are all done and satisfied that everything is working ok, you can delete the redundant local user accounts from the member server. Do not delete any special accounts used by services (e.g., used by Exchange Server or SQL Server). Q: I re-added my domain groups to the share-level permissions list for my shared folders and shared printers. (See previous question.) But my users report that they are still denied access. What is wrong? A: On your new member computer run USRMGR.EXE. Select the local computer. (Look at the title bar and check that it shows the name of the local computer not the name of the domain.) Click on Policies -> User Rights. For each domain group (e.g., "Domain Users") grant the User Right to "Access this computer from the network". Also add "Log on locally" if you want to allow your users to log on locally. Q: I have hundreds of file shares. Is there any way that I can preserve the share-level permissions so I don't have to re-create them? If you have numerous file shares and/or numerous groups listed under the file shares, you can preserve the permissions by exporting the registry key HKLM\System\CurrentControlSet\Services\LanManServer\Shares\Security. Do this before you run UPromote. After you rejoin the computer back to the domain as a member server, reload the registry key. This will restore the share-level permissions. Q: I demoted my BDC to a standalone server. However SRVMGR.EXE reports that it is still a BDC. This prevents me from rejoining the domain as a member server. What is wrong? A: This is usually due to a WINS server with out-of-date domain records. WINS will retain old records for 7 days before deleting them. After you demote the computer, you need to delete from WINS all domain records that have the computer's Internet address. The domain records will have type <1Bh> (PDC) or <1Ch> (PDC/BDC). To delete the domain records, run the WINS manager and locate each old domain record with type <1Bh> or <1Ch>. Right-click and select "Delete Mapping". Select "Tombstone" (not "Delete") so that the deletion will be replicated to all of the other WINS servers in your network. For technical details see Locating a DC and WINS. Windows NT Domain: If you are still having problems joining the domain, you can use NETDOM.EXE from the NT Resource Kit to force your computer to join the domain. On your standalone computer type the command NETDOM.EXE /DOMAIN:mydomain MEMBER mycomputer /JOINDOMAIN where mydomain is the name of your domain and mycomputer is the name of the standalone computer. Active Directory Domain: In rare cases you cannot rejoin the domain because of an error in Active Directory ("DSA: Object cannot be deleted"). This is usually due to recovery of the AD database to a state prior to when you demoted the BDC. You will need to manually remove from AD all the old references to the BDC. See Q216498. Orphan BDCQ: My BDC lost contact with the PDC. How can I demote the BDC without the PDC? A: UPromote will ask to contact the PDC in order to delete the machine account of the BDC. It will refuse to continue if it cannot locate the PDC. This problem can occur if you upgrade your Active Directory domain from "mixed" mode to "native" mode while one or more NT BDCs are still present. When you do this your BDCs will lose contact with the Windows 2000/2003 domain controllers. As a workaround, if your BDC becomes orphaned you can use the following procedure to demote it:
Afterwards you can rejoin the computer to the domain as a member computer. See Rejoining the Same Domain. GroupsQ: I used UPromote to demote my computer to a standalone server. What happened to my global groups? A: Global groups have no meaning on a standalone server. If users were an indirect member of a local group via a global group, UPromote will move the users directly to the local group. For example, if user Fred is a member of the global group Domain Admins, and Domain Admins is a member of the local group Administrators, then UPromote will move Fred directly under Administrators. Q: I used UPromote to demote my BDC to a standalone server and then rejoined it to the domain as a member server. I deleted all of the redundant local users with USRMGR.EXE. Later I tried to delete a redundant group. USRMGR.EXE refused, claiming that I needed to first remove all the members from the group. But I don't see any members. How can I delete the group? A: This is due to a Microsoft bug in USRMGR.EXE. If you delete a large number of users in a single session, USRMGR.EXE will sometimes forget to delete some of the group members. This prevents you from deleting the groups. To fix your password database, type the command PROMOTE.EXE -GROUPFIX. This will delete all of the "ghost" user members from your groups. (Note: Requires UPromote version 1.435 or later.) Backup and RecoveryQ: Why does UPromote back up the registry? A: The registry contains all settings required to create a domain controller. Most importantly, it contains the password database. Backing up the registry ensures that if a problem occurs during the upgrade you can recover your machine by restoring your registry. UPromote has been thoroughly tested and is safe and reliable. However factors outside of Algin's control, such as a corrupt registry hive or an unreliable disk controller could cause UPromote to fail. Q: How do I recover the registry? At the beginning of the conversion process, UPromote asks for permission to create an Emergency Recovery Disk (ERD). This is strongly recommended. If the conversion fails, you can restore the registry using the ERD. Use the following procedure to restore the registry with the ERD:
If you changed the SID, you need to restore the SID ownership of your files. To restore the ownership of your files, run PROMOTE.EXE -SID. Do this immediately after you restore your registry. If your computer was originally a BDC, you need to rejoin the BDC to the domain. On the BDC run the utility NETDOM.EXE from the NT Resource Kit. NETDOM.EXE BDC mybdc /ADD Where mybdc is the name of your BDC. If done correctly these steps should completely restore your computer back to its original state. Q: I created a BDC. I later changed my mind and demoted my computer back to a standalone server. What happened to my old user accounts? A: A BDC is a read-only replica of the PDC's password database. When you created the BDC, you overwrote the old local accounts in the registry with accounts from the PDC. The only way to restore the old local accounts is to reload the original registry. BDCs and NT ServicesQ: I promoted a standalone server to a BDC. After I rebooted, some of my services no longer start. What happened? A: A BDC is a read-only replica of the PDC's password database. When you created the BDC, you overwrote the old local accounts in the registry with accounts from the PDC. Most services run under the SYSTEM account and are not affected. However a few services may run under special accounts. (For example, Microsoft SQL Server runs under its own special account.) You need to recreate these accounts on the PDC. You also need set the the stored password for each service to match the password on the PDC. To set the stored password of each service,
Q: I promoted a standalone server to a BDC. After I rebooted, Internet Information Server (IIS) can no longer access the IUSR_ A: (Note: It is generally a bad idea to run IIS on a DC for security reasons.) A BDC is a read-only replica of the PDC's password database. When you created the BDC, you overwrote the old local accounts in the registry with accounts from the PDC. This includes the IUSR_ After you recreate the accounts, you need to tell IIS the passwords. To tell IIS the password for the IUSR_ To tell IIS the password for the IWAM_
Use the password you assigned when you created the IWAM_ Old NT Service PacksQ: Can I use UPromote with NT Service Pack 3 or earlier? A: NT Service Pack 4 (released in 1998) changed the internal format of the password database. The general rule is that all domain controllers must run SP 4 or later. This is a well known issue with NT (KB Q197488). UPromote will work with earlier service packs, and it will warn you if it detects two servers with incompatible service packs. Trust RelationshipsQ: When I try to downgrade my PDC, UPromote says that I must remove my Trust Relationships first. Why is that? A: Mainly for security reasons. A standalone server should never have a trust relationship with another domain. Compatibility IssuesNovell Directory ServicesQ: Is UPromote compatible with Novell Directory Services (NDS)? A: No. NDS changes the user password database structure. The changes are incompatible with UPromote. You must de-install NDS before using UPromote. Windows NT Terminal ServerQ: Is UPromote compatible with Windows NT Terminal Server? A: No. Terminal Server uses an incompatible password database structure. Compaq SMART RAID Disk ControllerQ: Is UPromote compatible with the Compaq SMART RAID disk array controller? A: The Compaq SMART RAID disk array controller has a known problem where it sometimes loses data when rebooting. This includes registry modifications. To prevent problems UPromote will warn you if it detects the presence of a Compaq SMART RAID disk array controller. For more information see Compaq SMART RAID. Windows NT Small Business ServerQ: Is UPromote compatible with Windows NT Small Business Server? A: No. SBS is hardwired to always act as a PDC. It cannot run as a BDC or as a standalone server. More InformationFor technical details on the operation of UPromote see UPromote Operation. For user feedback see UPromote Users. UPromote OperationOperationUPromote runs as a wizard application. It will ask you a series of questions, culminating in a final "Finish" button. UPromote makes no changes to your computer until you press the Finish button. When you press the Finish button UPromote will perform all of its operations and reboot your computer two times. UPromote will take anywhere from 5 minutes to an hour to complete. A large number of groups (more than 2000) and a large number of files (more than 200000) may take more than an hour. Small memory (under 128 MB) will also slow it down. When the message "Operation complete" appears, you can uninstall UPromote. Error ChecksWhile showing the wizard pages UPromote will perform several checks of your computer looking for possible errors that will prevent it from running successfully. These error checks are passive and do not modify your computer in any way. The error checks include the following,
You can override most of the error checks by appending the parameter -OVERRIDE to PROMOTE.EXE
Note: Override of error checks is not recommended. We cannot provide you with support if you encounter a problem while ignoring the error checks. License Activation CodeWithout a license activation code, UPromote runs in Demonstration Mode. The Finish button is disabled. When you buy a license activation code and type it in, UPromote will unlock the Finish button. If you purchased a single computer license, UPromote will check that the license activation code matches the name of the computer. ExecutionWhen you press the Finish button UPromote will start converting your computer. The exact steps depend on whether you are creating a PDC, a BDC, or a standalone server. The main difference between a standalone server and a domain controller (DC) is that a DC runs the NETLOGON service. The NETLOGON service authenticates passwords of users in the domain. Primary Domain Controller
Backup Domain ControllerTo create a Backup Domain Controller (BDC) UPromote executes the same steps as described above. It also executes the following additional steps:
Standalone ServerTo create a standalone server UPromote does the following:
These operations happen only on the local computer. For example if you are demoting a BDC, the users and groups are modified only on the BDC itself; UPromote does not modify the users and groups (nor any services or file shares) on the PDC. Security IdentifiersA security identifier (SID) prefix is a number that uniquely identifies a computer in a network. Each member computer in a domain has a unique SID prefix. The Primary Domain Controller shares the same SID prefix with its Backup Domain Controllers. In other words, all domain controllers in the same domain also share the same SID prefix. This makes the Primary Domain Controller interchangeable with the Backup Domain Controller. When you promote a DC, the SID prefix must be changed to match the other DCs in the domain. Conversely when you demote a DC, the SID prefix must be changed to avoid clashing with the remaining DCs. To change the SID prefix UPromote scans the entire registry and all of the files. It changes all of the registry keys and all of the files to use the new SID prefix. Security IDs and the RegistryUPromote does a simple search-and-replace of the old SID prefix in the registry. The SID prefix is encoded in 4 different formats in various keys in the SAM and the rest of the registry. (Tools such as Norton Ghost and newsid only recognise 3 formats, which is why these tools fail when used on a domain controller.) When UPromote finds a match it replaces the SID prefix with the new value. This simple operation has several side effects. For example, the access permissions for file shares are stored in the registry under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Shares\Security. The SIDs for the access permissions are changed just like any other SID. This is why the domain share permissions no longer work when you rejoin the computer back to the domain. As explained in the FAQ, you will need to run EXPLORER.EXE and re-enter the permissions for the domain groups to access the file shares. The SIDs for the user accounts in HKEY_LOCAL_MACHINE\SAM are changed as well. When demoting a BDC, the result is that the user accounts become local accounts with the same names as the original domain accounts. They become distinct accounts. They are not domain accounts even through they may appear superficially to be the same. If you rejoin the same domain as a member server, most of these accounts will become redundant and you can delete them. This can best be explained with an example. Let's say you have a BDC named B that you want to demote and then rejoin back to the same domain as a member. Because it is a BDC, machine B has an exact copy all the user accounts on the PDC (call it machine A). Each of these accounts has a unique SID. For example the user FRED has SID S-1-5-123456-1001. When you run UPromote on machine B, the SID for FRED on B is changed to a new random SID prefix: S-1-5-7890123-1001. The account DOM\FRED still exists unchanged on machine A. But the SID for account FRED on machine B is now S-1-5-7890123-1001. Both have the same user name but are now distinct accounts. As far as NT is concerned the two accounts are completely unrelated. B\FRED now owns \WINNT\PROFILES\FRED on machine B. When you log on to machine B with DOM\FRED it is as if he is logging on for the first time. Machine B will search the registry key HKLM\Software\Microsoft\Windows NT\Current Version\ProfileList, looking look for a subkey with SID S-1-5-123456-1001. It doesn't find one, so it creates a new profile for DOM\FRED at \WINNT\PROFILES\FRED.000. It stores a pointer to this new profile at HKLM\Software\Microsoft\Windows NT\Current Version\ProfileList\S-1-5-123456-1001, under the value name ProfileImagePath. Because DOM\FRED is logging on for the first time, WINLOGON.EXE on B will assign to DOM\FRED an initial profile. The new profile is copied from the Default User template at \WINNT\PROFILES\Default User\*. This is how DOM\FRED gets the initial set of icons on the desktop. Now remember B\FRED was originally DOM\FRED, and he had all of the original icons and application settings. But because the SID was renumbered, these are now owned by B\FRED. The physical files haven't moved; they are just owned by a different account (a local account). If you need to copy over the original icons and application settings back to DOM\FRED, log on to machine B with an unrelated account (e.g., Administrator) and type
This will copy over the icons and registry settings from B\FRED to DOM\FRED. (Note that the suffixes ".000" may vary. Inspect the registry value ProfileImagePath to determine the correct folder names for the source and destination folders.) If you no longer need the account B\FRED you can delete it. On machine B type NET USERS FRED /DELETE. Changing the Security ID on DisksIn addition to changing the Security ID (SID) prefix in the registry, UPromote will also change the SID prefix for files on the disk. The SID prefix in the Access Control List (ACL) of every disk file is changed to match the new SID prefix. In practice few SIDs are changed. The vast majority of SIDs represent well known groups that have fixed values. The well known groups include Everyone, Guests, Users, Authenticated Users, Backup Operators, Administrators, and System. These groups have the same fixed SID prefix worldwide. UPromote will not change these SIDs. Any groups that you created will have a unique SID. When you promote or demote a BDC UPromote will change the SID prefix for all of the groups that you created. By default UPromote will select all local disks. It will scan all local disks for files that contain an ACL with the old unique SID prefix and change it to the new unique SID prefix. Normally you can accept UPromote's defaults and simply press the Finish button. Important: There is one important exception where the unique SID prefix should not be changed. The exception applies if following conditions are all true:
If all of the above conditions are true, then you should consider not changing the SID on the disk(s) that contain the shared files. The reason is that the disk contains shared files that are owned by other users in the domain. If the SID prefix is changed, the users could lose access to their files. For each disk letter (D:, E:, etc.) select "Do not change these disks" on the SID ownership panel. This will leave the original domain SID prefix unchanged on those disks. You must always change the SID on your Windows system disk (typically C:). This is required for Windows to operate properly. If you mistakenly selected the wrong disks you can correct the problem by promoting the computer back to a BDC and then demote it again with the correct disks. When you promote the computer, select the same disk letters so that UPromote will restore the file SIDs back to their original values. Then run UPromote again to demote the BDC and select "Do not change disks" with the correct disks. Locating a Domain ControllerThe following information may help you troubleshoot problems with locating a domain controller. When you enter your password on the member computer, it attempts to locate a DC by broadcasting a NETBIOS packet of type <1Ch>. The packet contains the name of the domain. When a DC receives the packet it will respond with its name and Internet address. The member computer will then send the logon password (in a hashed and encrypted form) to the DC for authentication. The NETLOGON service will read the password, authenticate it, and send a response to the member computer. A member computer can also locate a DC by querying the Network Neighborhood (NN). The NN is a list of all computers on the local network. The list is maintained on a special computer called the master browser. The master browser is usually the first domain controller that booted on the network. (You can identify the master browser computer by running the console application NBTSTAT.EXE -a. The computer that responds with the record name __MSBROWSE__ is the master browser.) The Network NeighborhoodThe list of names in the Network Neighborhood will gradually expire after about an hour. To refresh the list each computer on the network periodically sends a NETBIOS broadcast packet, about once every 10 minutes. When the master browser sees these packets it will refresh the list of names in the NN. This is why the name of a DC remains in the NN for up to 60 minutes after you demote it with UPromote. The Server Manager (SRVMGR.EXE) uses the Network Neighborhood to identify the list of DCs. This is why you must wait 60 minutes after running UPromote before SRVMGR.EXE updates its list of DCs. If SRVMGR.EXE cannot find a computer in the NN, it will ghost the icon for the DC, indicating that the DC is offline. Even if you reboot the computer as a standalone server, Server Manager will continue to show a "ghost" icon for the DC until the time expires. Locating a DC and WINSIf your network is running a WINS server and your computer is configured as a WINS client, the steps for locating a DC are different. Instead of broadcasting a NETBIOS packet, the member computer will send a query to the WINS server. It will ask for a record that contains the name of the domain. The record must have type <1Ch>. (1C = DC, 1B = PDC). The WINS server will respond with the Internet address contained in the record. If the WINS server has more than one record, it will return one randomly. The member computer will then contact the DC as explained above. When UPromote removes a DC, it does not remove the the WINS record. UPromote cannot remove the WINS record because Microsoft does not provide a method to remove a WINS record programmatically. Therefore to remove the 1C and/or 1B record you must launch the WINS Manager and remove it manually. WINS is also used to update the Network Neighborhood (NN). Because WINS considers a DC record to be 'important', it will cache the record for up to 7 days before deleting it. During this time the ghost DC may continue to appear in the Network Neighborhood. Member computers will continue to attempt to authenticate with the ghost DC for 7 days. After a few seconds the attempt will time out and the member computer will then attempt to authenticate with another DC. This why after using UPromote there is sometimes a short delay of a few seconds when authenticating a password. The delay goes away after 7 days. (In rare cases the file LMHOSTS may contain the name of the DC. If the file contains a text line with #DOM, the ghost DC will be present in the NN as explained above, however it will never expire until you delete the text line from LMHOSTS with a text editor.) Cached PasswordsIf a member computer cannot locate a DC, it will attempt to authenticate the password using a local cache of the 10 most recently used passwords. The cache is stored in an encrypted form in the local registry. This is why if you demote the last DC, the orphaned member computers will still appear to be authenticating even though the DC no longer exists. To view the list of actual domain controllers run the console utility NLTEST.EXE /DCLIST:mydomain where mydomain is the name of your domain. NLTEST is part of the NT Resource Kit. UPromote UsersUPromote has helped many businesses, universities, and Fortune 500 companies. Those you may recognise include the following:
Feedback About UPromote"Excellent product! This utility was worth every penny. We saved hours in terms of time, and paid for the software 10 times over with the labor costs we saved by not having to reinstall." - M.D. "I purchased UPromote today and solved my server problems in 15 minutes! Thank you so much for such a great time-saving product." - N.M. "We realise we are using this tool on a larger scale than maybe its been used before, but the support we have received has been A+. Thanks for your help. Give yourself a raise! " - S.H. "WOW!!! HOLY SMOKES!! WHAT AN AMAZING PRODUCT!! THANK YOU. Okay I'll stop yelling now. This just saved our company about 8 hours of work!!" - J.H. "Thank you guys for this product. I had a rather difficult situation with a site where two domains and two domain servers had needlessly been set up... the server had some complex systems running on it and UPromote worked very well, saving days of building again from scratch.. Thanks again, would recommend it!!" - S.F. "The actual process took about 15 minutes ... Maybe you could provide some tech support lessons to some of these larger companies, since yours is outstanding!" - A.S. "This is not to bother you guys but to complement you all on a very very good customer service and support department. I have been in the IT industry for many years and I have to say that THIS IS THE QUICKEST I HAVE EVER SEEN. Many Thanks. A lot of other companies could learn from you." - E.S. LicensingThree licenses are available: Single Machine License Unlimited License WorldWide Maintenance is not available for UPromote. UPromote is delivered by an emailed license file which activates the downloadable demonstration. Single and Unlimited licenses will be delivered immediately on completion of your order. Worlwide licenses will be delivered within 24 business hours. Discounts are available for academic and customers with charitable status. Please Contact us for further information. RequirementsThe following OS's are supported:
The following OS's are not supported:
Printed from www.pnltools.com © 2008 PNLTools Limited. All rights reserved |