Q: I have not done the upgrade to Adv Server I have to some instructions on setting up a domain name. I can not seem to get any instructions on the net.
I have 5 + computers that would join the domain to a login script that would build equity and the like and authenticity of the user login password to get extra security. Ive only played around with Adv Server once and have not had time to watch it because I do not want to mess my server because it is finally running well. I tried to setup a domain name once before and it needed me to get my system to convert to NTFS so that it is a domain, I was on the right track? Can anyone give me some detailed instructions or me in one direction for a number of detailed instructions, because I need help.
And If anyone has any idea how to do this, there are more options that users should log into their workstation with a username and password would be stored on the server?
Hope I explained that well.
Best Answer: Are some workstations using "simple file and print sharing" and some not? If the're using windows xp home they will by default, but xp pro will have the option to use simple file sharing or not. If they are not all using the same they won't all work.
Thats my only suggestion,
good luck
/hello there
Re:Well most of my PC's are 2000 and XP, btu I have 2 that are NT4 and 1-98, 1-Me,but they are all mine, no one elses, so I guess Im reasonable skilled!
I have it just for fun though, gotta learn it sometime, and at my leisure is better than my employers orders!
Re:First off, Advanced Server and Active Directory have NO corelation. One is a particular version of Server OS Code, and the other is an Application.
for guy, if you have all W2K clients, you shouldn't need to time sync them, it's built in to the OS authentication. Also, it's easier to just have the clients "remember connections", that way you don't have to script all their drive mappings. Well, it's only easier if you have users who are reasonably skilled w/ computers.
In W2K, you have to have an IP Domain Name, as it is now the same as the Windows Domain Name.
Re:First off.. I don't quite understand why you are trying to upgrade to Windows 2000 Advance Server when clearly your needs will be met by a normal server which is about 1/3 or more of the cost.
Next off you run a dcpromo on the Window 2000 Server and it will upgrade that installation of Windows 2000 Server to a Domain Controller and Install Active Directory if it isn't already installed.
After that you will need to read up on how to configure the server to fit your needs.
Re:I think your trying to do the same thing I did, jsut for home use, it was pretty easy actually.
Run the Configure your server wizard (or dcpromo if you prefer that way), setup a domain name for your domain, Ive used several over the last 2 yrs when doing my home stuff, Residential.local, Technology.home,TechNet.home, NoOneHome.local,etc.
You have to setup DNS on the Adv Server, it should be the DNS for the home LAN clients, they should use that for DNS, not the ISP's DNS, I have my clients set to use my server for 1st DNS and then the 2nd one is my ISP.
You can setup shares on the server, set permissions as you see fit, and then use Group Policy (via the Domain Security Policy in Admin Tools),
In the Group policy, you can specify the logon and logof scripts (I used .VBS ones for my drive mappings and printers, (email me if you want to have them), I also used a .BAT file to sync the time across my domain at login on all PC's.
Youll want to use all NTFS partitions though.
It also is my VPN server and web server and backup depository for my PC's
To be real simple, you can just have a domain setup and use a simple .bat file to map drives and printers and use the server for just authentication, but heck, its fun to use it as much as you can if you got it.
Re:Woo wooo wooo….Back the truck up.
All I need is a Domain that the client workstations would log into on the inner network (intranet). I don't want to buy a domain name or anything I just want to have it so that people have to log into the network to use the computer.
Re:There is no such thing as PDCs and BDCs with Windows 2000 Server and Active Directory, unless you have exisiting NT servers and you stay in mixed mode. If that is the case, the NT PDC must be upgraded first.
The poster didn't indicate that he had any NT servers, so I am assuming this will be a native mode domain. In native mode, there are only DCs. It is generally advised to have more than one DC for load balancing and redundancy purposes, but all DCs in Active Directory contain a read/write copy of the directory, which contrasts with NT PDCs holding the only read/write copy of the SAM, and BDCs holding a readonly copy.
The only distinctions between 2000 DCs are the FSMO roles that they hold. There are five (I'm not going to get into detail, do some reading), two of which must be unique for the forest, the other three must be unique for each domain in the forest.
Re:to add: I believe a PDC has to be set during the install process…only BDC's are doable after.
They also DEFINITELY need a static IP…..If you are behind a DHCP router, just type in any staic IP address as DHCP will just ignore it….
The NAT will take care of internet access.
P.S.
PDC = Primary Domain Controller
BDC = Backup Domain Controller
![]()
Re:Thanks I check into this tomarrow after I get off work
Re:Creating a domain on Win2k server/advanced server means installing Active Directory. This is done by running the dcpromo command from the run dialog.
Of course, there is a little more to it than that. You have to have your DNS set up, and you have to have decided on what your domain will be called. On that note, is this domain going to be behind a router on a home network, or accessible to the Internet. If its the latter, you need to register a domain name (www.xyzz.com). If its on a home LAN, you can choose anything, but I would suggest something that doesn't work on the Internet, such as testdomain.test.
And yes, you will have to convert at least one partition to NTFS. You should be using it on all your partitions to begin with if you are running AS, unless you are dual-booting. And if you are running AS, you shouldn't be dual-booting.
I would suggest you dig through TechNet a bit before you dive into this little project. They have some pretty detailed walk-throughs on this and other procedures. You may even want to invest in a book or two. My recommendation would be 'Mastering Windows 2000 Server' by Mark Minasi (4th ed.). You can also check out his website (www.minasi.com), which includes a very useful forum.
Oh and make sure that any data you might want in the future that is on this server is backed up before you do this.
0 Comments.