Zartach

Search on the forum for toothpaste to fix scratched cd's might be able to save your original copy to be able to make a backup from that one via that trick ..

Replication works with version numbers, the online DC's have a higher number so no 'old' data will ever overwrite the 'new' data. the old dc would be treated as it would have when there was no data on it, the thing has nothing to add to the ad since its version number is too low. It would actualy grab replication from the other dc's and overwrite its own 'old' data.

There are absolutely no Event messages occuring ? - Check network with ping utility, test from client to server and from client to target. - Check if you can resolve hostnames NETBIOS/DNS maybe the problem lies in one of the above .. Hope it helps,

A lot of spyware will not work on windows NT4, and win9x even. One customer i work for stubbornly uses both OSses still and reguarly i have to do some cleaning (public internet pc's) to clean spyware. I have seen some annoying ones work on them but a lot less than on XP, It is true that if there is a critical vulnerability you might not have the proper defence as XP would recieve a patch but a good virusscanner can help there. I would not place any buissness critical / secret info on those systems though.

You say that all the components loose connection at some point ? If it was a NIC it would only be one pc, or server. It makes no sence that routers loose connections as well if it is a NIC problem. You could check for collision on the network, but i have not seen that be a problem for a long time. If you have Cisco network equipment you can check if Spanning Tree is actrivated, this caused problems for a customer of mine and Clients would loose network access above OSI lvl3 (so no more filesharing/printing but still pingable) Other than that, i would involve a company that can do measurements on the physical network to check if there is a short or something. It is possible that you need to upgrade the wiring to cat6 (shielded utp) if you are in a heavy industrialized area, or are located close to high voltage powerlines. I guess if you want NIC diagnostics you can script it with WMI local and have it send the results to a server or something, no idea if something like that exists allready. I doubt you can get the info you want from it though. Last call would be to check for events on servers/clients that show nic failiure, you need to script that too i guess. Hope it helps a litte,

To migrate from windows 2000 functional level to Windwows 2003 functional level you will need to run adprep, when you set up one of the 2003 servers as a DC. This sounds a lot more scary than it actually is though. It is reccomended you run the FSMO roles on 2003 after upgrading. Wait for it until you _know_ the replication has finished though. This article describes how you can move or sieze them: http://support.microsoft.com/kb/255504/ Seizing them is more intrusive, and is not reccomended unless you had a major crash and are otherwise unable to restore theold server. For reccomendations and info on FSMO roles: http://support.microsoft.com/kb/223346/ Be carefull if you have an exchange mail environment and follow these steps to prevent problems in the schema regarding exchange: http://support.microsoft.com/kb/314649/en-us Hope it helps,

Running a sccript agains the AD should not require a username or pasword, are you running the script from a pc thats a member of the domain ? can you try running it on a DC ? I have numerous scripts running collecting info and sometimes adding info to the AD and had never had problems with having to autenticate.

My guess is its a time out on nameresolution or something, i have seen it happen sometimes that a network drive would recieve a generic name but it does not happen often in my environment. You could check if the server is really busy or something or check if theres any errors in the eventlog around logon times.

Are you upgrading on the DC that has the role schema master ? and are you upgrading using the domain administrator account ? If all else fails you can try and sieze the roles and clean the metabase before upgrading, but beware that if you do that you need to disconnect the old role owners and demote them before adding them back to the domain. Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller http://support.microsoft.com/default.aspx?...kb;en-us;255504 How to remove data in Active Directory after an unsuccessful domain controller demotion http://support.microsoft.com/?id=216498 Hope it helps,

Check for any errors in the eventlog, there may be an error logged there.

I will try to make a little script for it, but it wont be befone tonight as i have to test it and my testing machine is at home

Sorry mate, this won't go on a web edition server, quoted from MS: Note: Neither Certificate Services nor Web enrollment support is enabled on Windows Server 2003 Web Edition. You can however have your own Certificate rootserver, there will be a message saying to the user that the certificate is unsigned but you can circumvent that by configuring your company as a trusted certificate source - i dont remember exactly where though - The following doc can help you out on how to create certificates for your site on web edition, http://www.microsoft.com/technet/prodtechn.../webenroll.mspx

Theres a couple of articles on Technet about this error: For SBS theres one that suggests nothing is wrong providing the error occures ar startup and shutdown (the AD would be closing before or started after Exchange) http://support.microsoft.com/default.aspx?...kb;en-us;828051 Then theres two that refer to misconfiguration or after a DC was demoted: http://support.microsoft.com/default.aspx?...kb;en-us;272552 http://support.microsoft.com/default.aspx?...kb;en-us;223346 Hope you can fix this with these articles,

Microsoft has an article about this error and reccomends you install the latest Service Pack. http://support.microsoft.com/default.aspx?...kb;en-us;815140 Hope it helps,

Yup, You can use dsadd from the commandline : http://technet2.microsoft.com/WindowsServe...3.mspx?mfr=true Have fun,

I dont know if this program can use usernames and passwords but that printer on the server is not accesible by anyone, you need to authenticate. You can if the program allows you specify the proper username and password for the printer. Or change the permissions on the server so that the object 'everyone' has print rights. Hope it helps,

Do you get events in the eventlog from this? if so please post them, maybe they can shed some light on the problem.

Cool, nice script, its a better way than the batch i found. I like the input of the computernames in the txt file that way you can use a selective export to change the pwd on. Thanks for the script great stuff.

Hello, the 1007 is a general error and it is seccond to the 2003 error, in your case there is a "library Validation Code"for the ASP service, this subkey is checked against the file creationtime and some other properties of the dll. If they do not match (the hash of the file differs from the one in the registry) you get this error. If you reinstall the asp service it will be solved, you can do that via the control panel, software, windows components and from there select the details of the IIS and deselect ASP. and after that follow the same procedure to reinstall it by selecting it again. Hope it helps,

If this is occuting for people connecting from the internet it may be that you need to enable Out of Office reply for internet on the server. See : http://support.microsoft.com/?id=262352 If that fails it may be that there is a corrupt rule in the users inbox and you need to remove all rules. Some MS dev made a solution for that via a support tool ( an article thats been hiding on my HD for a while ) This is because when a rule is created it creates a mirror one that is hidden from theuser if one of these gets corrupted or they fail to synchronize the rule wont work and manual deletion sometimes fails to delete the mirror rule. 1. Find mdbvu32.exe in the \support\utils directory on any of the Exchange Server CDs. 2. Run mdbvu32.exe. 3. Click OK to clear the first window that pops up. 4. Make sure that your profile is selected in the Choose Profile window and click OK. 5. Click on the MDB menu option. 6. Click on the OpenMessageStore option. 7. Make sure that "Mailbox- [user's full name]" is selected and click on Open. 8. Click on the MDB menu option again. 9. Click Open Root Folder. 10. In the Child Folders box - double click on "Top of Information Store". 11. In the next Child Folders box - double click on "Inbox". 12. Look in the Associated Messages in Fld box. All of your rules are in this box. 13. Once you find the rule that you want to delete then close the properties for that rule. 14. On the MAPI_FOLDER page make sure that the rule that you want to delete is still highlighted. 15. In the "Operations available (select operation, then push Call Function button)" text box, push the drop down button to reveal the list of functions. 16. Scroll down the list of functions until you see "lpFld -> deleteMessages() (ON SELECTED MSGS)" and then click on it to select it. 17. Next press the Call Function button. This will delete the rule that you selected. 18. Press the Close button to exit the MAPI_FOLDER window. 19. Press Close again to exit the next window. 20. Press Close again to exit the last window. 21. Click on the MDB menu option. 22. Click Store Logoff. Then click OK and OK again. 23. Click Session and then click on Exit. Hope it helps,

Allready andswered you in this post: http://www.msfn.org/board/index.php?showtopic=75096

Those are NTFS permissions, the share permissions can be viewed via the share tab andd pressing the button permissions on that tab. Zar

Are you sure that the 2 disks are excactly the same size ? Microsoft reccomends to use the same type of disk made by the same vendor because sometimes when they say its yay big it is actually a little diffrent.

On NT4 you dont really want to rename the domaincontroller or the domain, its just too inconvenient in my experience. You can reinstall the services via the control -> panel software -> windows components. i believe. been a while since i installed one tho and i dont have a VM running NT4 at the moment. However, you might want to try simple solutions first like dropping the computeraccount from the domain and rejoin the Winxp machine into the domain. You should also check WINS via the administrative tools to check if the addresses are set up correctly, WINNT does not lean heavily on DNS though so it should not generate too mutch problems. But you can always change the configuration via the DNS tool. for WINS i believe you should see the servername and the domainname pointing to your server IP address, i cant remember any other requirements at the moment. Nothing should have changed in the TCP/IP configuration except for the name of the server but you can check the TCP/IP via the properties of the netword card. But as i said it may all be simple and you may just need to rejoin the PC to the domain.

Might be a faulty CD, check the disk for scratches and so if it is not scratched and does have those problems you might want to try and contact Microsoft to get a replacement. Zar