There are some roles that run on the first DC that you will need to move, like the PDC emulator and global catalog, if you are going to completely demote it.
If you already have a server running 2000, all you have to do is run DCPROMO to promote it to a DC. Make sure you have active directory running properly. Check your event logs on your current DC and make sure you aren't receiving any AD/DNS errors. If you have multiple servers available you...
We've been fighting with SBC for 2 months now trying to get VPN to work over DSL. All of our cable user get in without a hitch but DSL just won't work. We're using a Cisco concentrator with the Cisco client. If anyone knows of a solution I'd like to hear it too. :-)
Sysinternals has a utility called BGInfo:
http://www.sysinternals.com/ntw2k/utilities.shtml
I use it on all my servers to show the servernames, ip addresses, service packs, and other info.
Sysinternals has a lot of other tools you should check out too. :-)
Check out Hyena from systemtools.com. You can move printers and shares from one server to another. I used NTBackup to move the data and security settings and then used Hyena to move the shares over. It copies the security from the shares also.
Actually, what you need to do is create Sites for each of your remote locations in AD Sites and Services. Here's an article that explains Sites:
http://www.windowsadvantage.com/tech_edge/05-15-00_understanding.asp
And here's M$ link on how to create Sites...
Create a new website and name it MyWebsite and copy your files to it. In DNS add a host record called MyWebsite and point it to the address of the webserver. IIS knows to route the request to MyWebsite.
You're talking about several different licenses. First you need 5 licenses of Windows 2000 Server. Net you need 500 Client Access Licenses (CALs) for your workstation. Every workstation that connects to a server will need a CAL. The servers all need to be in Per Seat licensing mode. If you...
Hey everybody,
I've come across a rather interesting problem. We migrated a file and printer server to a new server. All of the printers were shared out the same on the new server. We used the same name on the new server to prevent mapping and printer issues. The thing that was really messed...
If you want to setup a specific printer you can use vbscript. Save the following as a .vbs file and make the appropriate changes for your printer:
'Start Here
MsgBox "Creating Printer ..."
strPrinterPath = "\\MyServer\MyPrinter"
Set WshNetwork =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.