G
Guest
Hi
I have 2 DC in my company. Lets call it ServerA and ServerB. ServerA was the initial server with all the 5 FMSO roles. However, last week ServerA hardisk crashed. (2 of the 3 hardisk configured as RAID 5 crashed at once!! - The machine is from a reputable company but i shalln't disclosed it. Btw the machine is only 6 mths old. Sheer bad luck). I don't have a full backup of the system. Only data backups. Anyhow i have replaced the hardisks and re-installed the OS. i run DCpromo and make ServerA back as a DC. ServerA manage to "Synchronised" with ServerB during DCpromo. All users and computers appear in ServerA after the DCpromo. However, if i were to create a new user in ServerA, i will received event error id: 16650. After i ran ndsutils and seize the "Infrastructure master", "PDC" and "RID master" roles, i did not have the event id: 16650 error and i could create users in ServerA.
After the above seizure, i received 2 FMSO errors instead of 5 which is the "Schema master" and "Domain naming master" roles. In my situation, could i seize the remaining roles from ServerA. What will happen to ServerA? Will it still be a DC? Will i have to DCpromo ServerA again to demote it and then run DCpromo again to "join" back as a DC? If i were to do just that, will all the softwares and folders still remain intact. (i only have Terminal Server licencing, Symantec Antivirus and user data in it)According to an article in Microsoft Knowledgebase, it is not recommended to seize all the roles unless i want to put ServerA permanently out of the domain. In which case i'm not but in fact trying to re-instate in into the domain
PLS HELP. GREATLY APPRECIATED!!
I have 2 DC in my company. Lets call it ServerA and ServerB. ServerA was the initial server with all the 5 FMSO roles. However, last week ServerA hardisk crashed. (2 of the 3 hardisk configured as RAID 5 crashed at once!! - The machine is from a reputable company but i shalln't disclosed it. Btw the machine is only 6 mths old. Sheer bad luck). I don't have a full backup of the system. Only data backups. Anyhow i have replaced the hardisks and re-installed the OS. i run DCpromo and make ServerA back as a DC. ServerA manage to "Synchronised" with ServerB during DCpromo. All users and computers appear in ServerA after the DCpromo. However, if i were to create a new user in ServerA, i will received event error id: 16650. After i ran ndsutils and seize the "Infrastructure master", "PDC" and "RID master" roles, i did not have the event id: 16650 error and i could create users in ServerA.
After the above seizure, i received 2 FMSO errors instead of 5 which is the "Schema master" and "Domain naming master" roles. In my situation, could i seize the remaining roles from ServerA. What will happen to ServerA? Will it still be a DC? Will i have to DCpromo ServerA again to demote it and then run DCpromo again to "join" back as a DC? If i were to do just that, will all the softwares and folders still remain intact. (i only have Terminal Server licencing, Symantec Antivirus and user data in it)According to an article in Microsoft Knowledgebase, it is not recommended to seize all the roles unless i want to put ServerA permanently out of the domain. In which case i'm not but in fact trying to re-instate in into the domain
PLS HELP. GREATLY APPRECIATED!!