<div>
Are you talking about the time it takes for a domain user to boot and logon? 
</div>


<div>
That's in group policy BTW &nbsp; ^<br />

</div>


<div>
Actually, to make it faster, you want to DISABLE that setting - having it enabled makes the user wait until network services have started and computer policies and startup scripts have been processed before presenting the logon screen.<br />
<br />
However, I'd still like to know if this is what you are talking about - we're assuming by giving this advice that you are in an Active Directory domain and not just trying to improve the time it takes to access a stand-alone server.
</div>


<div>
WRONG!!!!<br />
<br />
You may experience extremely long delays (up to 5 minutes) when logging into domains using Windows XP Pro. &nbsp;This is caused by the asyncronous loading of networking during the boot up process. &nbsp;This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready. To disable this &quot;feature&quot; and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. &nbsp;Under Computer Configuration--&gt;Administra<wbr />tive Templates--&gt;System--&gt;Logon<wbr />, change &quot;Always wait for the network at computer startup and logon&quot; to ENABLED<br />
<br />
<br />

</div>


<div>
Here's the MS KB regarding this setting - <a href="http://support.microsoft.com/kb/305293" rel="ugc">http://support.microsoft.com/kb/305293</a>&nbsp;- by default XP has this setting disabled (when it's disabled it's referred to as XP Professional Fast Logon Optimization). &nbsp;In essence, if you ENABLE the setting, you force the PC to WAIT until the network services are fully loaded before allowing you to logon.<br />
If you make certain that the setting is DISABLED, then you DON'T HAVE TO WAIT until the network services are up before you see a logon dialog. &nbsp;At this point, you are logging on with cached credentials and GPOs and scripts are processed once the network services are up and the PC can communicate with a domain controller.<br />
Also, keep in mind that there's a cost to allowing Fast Logon - namely that any GPO &quot;changes&quot; will not get applied until after the user has logged on (not to mention the issues associated with software installation and folder redirection GPO's. &nbsp;In the environments I've worked in this hasn't been an issue as they don't change their GPO's frequently - but you have to determine if that's an issue for you.<br />
<br />
One more thing since you are seeing conflicting comments (mine and dstewartjr) - test this for yourself. &nbsp;I'm confident in my understanding, but it wouldn't be the first time I was sure I was right and turned out to be mistaken - or miscommunicated.<br />
I hope this helps.
</div>


<div>
Let me correct one thing I said - the GPO &quot;changes&quot; will LIKELY not get applied until after the user has logged on. &nbsp;If the user logs on right at boot time, then computer policies and startup scripts get processed in the background at the same time the user is accessing the desktop. &nbsp;However, if the user turns the PC on and leaves it at the logon screen for a length of time (doesn't log on right away), computer GPOs and startup scripts will get processed before they logon, simply because in that time the network services get started and GPOs processed.<br />
<br />
Also, I have observed that if the user's Active Directory user object has anything set in the profile tab (like mapping a drive letter to a &quot;home&quot; folder or specifying a logon script), then Fast Logon is pseudo disrupted - the user gets their logon dialog nice and fast, but will wait for Computer policies and startup scripts to process before the desktop comes up. &nbsp;So, to clear that delay out, make sure that there are no entries in the profile tab (use a GPO or some other method to get a logon script and/or that drive mapping handled).
</div>


<div>
I REPEAT VERY STRONGLY<br />
&nbsp;<br />
WRONG!!!!<br />
<br />
You may experience extremely long delays (up to 5 minutes) when logging into domains using Windows XP Pro. &nbsp;This is caused by the asyncronous loading of networking during the boot up process. &nbsp;This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready. To disable this &quot;feature&quot; and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. &nbsp;Under Computer Configuration--&gt;Administra<wbr />tive Templates--&gt;System--&gt;Logon<wbr />, change &quot;Always wait for the network at computer startup and logon&quot; to ENABLED <br />

</div>


<div>
Our environment:<br />
&nbsp;<br />
&nbsp;<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2009/01_w02/93334/Wait.bmp" target="_blank" class="file-inline" title="wait (640 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Wait.bmp</a>
</div>


Wait.bmp

<div>
DSTEWARTJR - I'm not accusing you of being wrong - I have no reason to doubt that this works best in your environment. &nbsp;<br />
All I can say is that I've worked on this in multiple enterprise environments and they improved their boot and logon times by DISABLING the Always Wait for Network at Startup and Logon. &nbsp;Of course, every environment is different, and you may have something else happening on your workstations causing the delay you mention.<br />
<br />
My understanding based on first hand experience and multiple MS docs about this feature, boot processing, and GPO processing has led me to understand that if the setting is enabled, the user will wait until network services start before seeing the logon dialog (due to Synchronous processing). &nbsp;Disabling the setting allows the policies and scripts to process Asynchronously and doesn't force a wait - it presents the logon dialog quicker.<br />
<br />
Can you clarify why there's a delay by forcing the user to wait and can you cite any MS or other references to support what you are putting forth.
</div>


<div>
Well it's been my experience that (taken from <a href="http://technet.microsoft.com/en-us/library/cc787386.aspx" rel="ugc">here</a>) <br />
&nbsp;<br />
&nbsp;<br />
&quot;In situations where you need for users to receive software, implement folder redirection, or run new scripts in a single logon, apply a GPO with the setting Always wait for the network at computer startup and logon to the computer.&quot; &nbsp;<br />
&nbsp;<br />
And most environments are using either software,folder redirection or scripts.<br />

</div>


<div>
OK, so your concern is not impacting software installation, implement folder redirection, and running new logon scripts.<br />
<br />
If the environment is using these options via GPO and making frequent changes, then yes, I agree that you should enable the setting so that the users process the changes at next logon (rather 2 logons later). &nbsp;But that does not improve boot speed which is what the question is about.<br />
<br />
The key phrase that comes into play is &quot;making frequent changes&quot;. &nbsp;For example, if you have your scripts and GPOs set, then you are dealing with forcing two logons in order for the client to process a new script, install a piece of software, or to have their folders redirected. &nbsp;If the changes are infrequent, then it's not a dramatic inconvenience. &nbsp;And if none of those 3 are a concern in the environment, then theres absolutely no reason to have Fast XP Logon.
</div>


<div>
 &quot;But that does not improve boot speed which is what the question is about&quot;<br />
&nbsp;<br />
&nbsp; How can I make clients log on faster to server? <br />
Question: How can I make clients log on faster to server? <br />

</div>


<div>
Valid point. &nbsp;I never saw an answer to my first response - so I'm working from my understanding of the question. &nbsp;In fact, aside from the question, it's just been you and me talking :)<br />
<br />
Please don't take any offense to my posts - because none is intended. &nbsp;I'm just sharing my thoughts and experience.
</div>


<div>
Ditto!!! &nbsp; :) and none taken
</div>


<div>
Does anyone have a script batch or vbs that I can use? 
</div>


<div>
jeamrotae, can you describe the situation with a little more detail? &nbsp;What is your environment and is it boot and logon that is slow or just logon or are you looking to automate something that the users have to do manually?
</div>


<div>
what would you like the script to do?<br />

</div>


<div>
 I simply (hopefully) would like for the workstations not to take so long logging on when a user tries to use their account. &nbsp;Now when a user tries to log on it takes forever.<br />
<br />

</div>


<div>
a script wont help with that, lets find out a little more info about your environment. Do you have any scripts that run at logon? Do you have a lot of group policies? Do you have software deployed thru gpo? Do you use roaming profiles or redirected folders?<br />

</div>


<div>
Their are scripts that run at logan, many group policies and redirected folders.
</div>


<div>
Ok, did you try the setting up above that I kept mentioning to start?<br />
<br />
<a href="https://www.experts-exchange.com/questions/24037457/How-can-I-make-clients-log-on-faster-to-server.html?cid=238&anchorAnswerId=23336505#a23336505" rel="ugc">https://www.experts-exchange.com/questions/24037457/How-can-I-make-clients-log-on-faster-to-server.html?cid=238&anchorAnswerId=23336505#a23336505</a><br />
<br />
<br />

</div>


<div>
Next how is your DNS setup?<br />
<br />
is it pointed at your ISP or itself(127.0.0.1) &nbsp;&lt;&lt;it should be itself<br />
<br />
Are your forwarders set to your ISP? &nbsp; &lt;&lt;it should<br />

</div>


<div>
what are your clients settings for dns, are they pointing to your DC?<br />
<br />
if not that would cause a big delay<br />

</div>


<div>
I won't go there until Monday so I did not try the first answer you mention but I will first thing. I guess I have to make a GPO for that setting. I was the original person to setup the server. I am just helping a friend get the network online again because the computers were moved from another building.<br />
<br />
Yes the DNS is pointing to itself (127.0.0.1). I never checked the forwarders but I was told by a network administrator (helpdesk) the dns suffix to put into the server and workstation. Since then everything goes online but this users take long to log on their accoutns.<br />
<br />

</div>


<div>
The clients should be using internal dns and the DNS should be using the ISP for forwarders. If not it will make a big difference.<br />

</div>


<div>
I will try that. I am not sure if I will be able to get the ISP IP. I will try ipchicken or something like that to get it but the network has firewalls. It is protected by ISA Server and Websense.<br />
<br />

</div>


<div>
you can also use 4.2.2.2 and 4.2.2.1 or take a look at opendns<br />

</div>


<div>
Whats 4.2.2.2 and 4.2.2.1......are you saying I can also use this as I can use 127.0.0.1?
</div>


<div>
 4.2.2.2 and 4.2.2.1 are dns servers that you can use for your forwarders<br />

</div>


<div>
How are the clients getting their IP addresses since they've moved? &nbsp;Is it DHCP from the server(s) that you moved? &nbsp;Is it DHCP from some device in the new building that was already there? &nbsp;Or, are you setting each one manually (yuck) at the workstations?
</div>


<div>
mlongoh:<br />
DHCP is handle by the major network/Cisco Routers in the building. <br />
<br />
The server I am working with is not a DHCP server. It is just a server put into the room along with 30 other computers. 
</div>


<div>
you'll probably have more success letting your server handle dhcp<br />

</div>


<div>
So the next question is what DNS server(s) are being set by DHCP - or are the workstations hard set to use specific DNS servers? &nbsp;And is the server that got moved acting as a Domain Controller and/or a DNS server?
</div>


<div>
dstewartjr: <br />
Are you suggesting I route (RRAS) from the server and make it a dhcp server?<br />
<br />
(Note the network in the building (school) is a internal network. I am working in a classroom within the school that is networked and monitored from remote locations. <br />
Administrators for the school's or schools( because they are support through many schools) &nbsp;network do not support classrooms creating their own domains or schools creating their own domain for several reasons. Two reasons &nbsp;there are no support or time to trouble errors. Normally servers put into &nbsp;classrooms are the schools' responsiblity not the School department. <br />
By the Administrators I was told the DNS suffix that all the workstation must use to get online.)<br />
<br />
&nbsp;<br />
<br />
As a flavor, I am helping a Teachers &nbsp;who use this classroom and have not been able to use the computers for months to get the server back online for the students to do their work and save it.
</div>


<div>
is this DNS configured on the machines or on the router?<br />
<br />
You could also edit the lmhosts file<br />
<br />
<a href="http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_evbs.mspx?mfr=true" rel="ugc nofollow">Using the LMHOSTS File to Find Computers and Services</a><br />

</div>


<div>
As it is in the classroom, all the computers have I changed the dns suffix to what the administrator for the schools told me for this particular school. After that I was able to log onto the &quot;server into the room's&quot; domain. (Note all computers are on dhcp configuration, no static ips or configured dns.)<br />
<br />
The&quot; server in the classroom&quot; has a static ip from the school dhcp/network and DNS 127.0.0.1.<br />
<br />
My problem was that the teacher was complaining that the students log in takes long.<br />
<br />
I am hoping if when I follow your suggesting and create a GPO policy for all users in the domain to: Computer Configuration--&gt;Administra<wbr />tive Templates--&gt;System--&gt;Logon<wbr />, change &quot;Always wait for the network at computer startup and logon&quot; to ENABLED. <br />
<br />
I am hoping this will help.<br />
<br />
I am not sure if I should use the open dns 4.2.2.1 and 4.2.2.2 as fowarders on the server. Do you still think I need that or it may help faster log in?
</div>


<div>
<b><u>YES !!!</u></b> &nbsp;you need the forwarders<br />

</div>


<div>
What I'd like to know is if the DNS server that the workstations are pointed to is the server or is it some other DNS server.<br />
I'd also like to know if the server is running the DNS server service.<br />

</div>


<div>
mlongoh:<br />
<br />
Server's forwarders are pointing to the school's dns. Server has static ip and a 127.0.0.1 dns. Server is setup for a domain within the school's network. The dns server configured on the server is the same as dns suffix which comes from school's main server in another room.<br />
<br />
dstewartjr:<br />
I am scared try the open dns because the server is configured as the same as all schools servers in a classroom settings. The intergators setup the server and leave the rest to non technical. <br />
<br />
I am figuring server was working well at another location so I have to tweak. I follow your suggestion for the GPO policy but did not test it yet because I am reimaging all the workstation and then joining them back to the domain.<br />
<br />

</div>


<div>
Sorry, I'm still unclear. &nbsp;What do the workstations think their DNS server is? &nbsp;Are they pointing the to Microsoft server that you moved? &nbsp;<br />
If not, you may wish to configure the workstations to point to the server that's closest to them (which would be the server in the same room on the same local network segment). &nbsp;This could possibly improve your network speed, and you could easily test it by hard-setting the DNS value(s) on the workstation and comparing logon from it versus what you've been seeing. 
</div>


<div>
mlongoh<br />
<br />
Can I configure the workstations for the Server/Dns server in the room for &nbsp;a dns of 127.0.0.1 without having to make static addresses for each workstation?<br />
<br />
Note Server in room is not a dhcp server.
</div>


<div>
use group policy<br />
<br />
<a href="http://support.microsoft.com/kb/294785" rel="ugc nofollow"> New group policies for DNS in Windows Server 2003</a><br />
<br />

</div>


<div>
At an XP workstation you would open the Control Panel and then the Network Connections. &nbsp;Right-click on the Local Area Nework connection (or whichever connection is the one that is connected to the network) and choose Properties. &nbsp;Then scroll down to and select Internet Protocol (TCP/IP ) and click the Properties button. &nbsp;I'm expecting that Obtain IP Address Automatically is currently select and that Obtain DNS Server Address Automatically is selected. &nbsp;Change the DNS to User the following DNS server addresses and enter in the IP address of the server in the room.<br />
<br />
Save the change and reboot and see if that improves your logon. &nbsp;This is assuming that the server in the room is a DNS server (and hopefully is also a Domain Controller).<br />
<br />
Let me know how you fare with testing that. &nbsp;If it works, you can do this at every workstation using the method I just described or use dstewartjr's suggestion, which could save time.
</div>


<div>
mlongoh:<br />
<br />
Because I was having trouble routing with my laptop ( I reimage computers with my laptop many at time &nbsp;by using my laptop as a dhcp server/router(RRAS)). Instead, I am using the Server in the room as a Dhcp server/router so I going to see Tuesday if this will make help logging on ,too. So thereforth, I will do what you suggested before that the server should being a dhcp server because I feel it safer to make static ips now on all the workstations and change the dns to 127.0.0.1.<br />
<br />
But my only concern is that I hope the workstations can get internet &nbsp;from the server in the room. <br />
<br />
The Server in the room - As it now, the server has a static ip from the schools network which is reserved for servers in schools ( told to me by the network administrator),also the server has a dns 127.0.0.1 and, the school's internal DNS Servers forwarders 10.X.X.X and dns suffix which was told to me by network administrators in order for the server to go online. Also, I was told to put this dns suffix on every workstation. And afterward join to the domain. But, having a domain and dhcp server/routing are not supported if issue occur. <br />
<br />
Hopefully, Tuesday all this will work out.
</div>


<div>
Just to clarify, the server should be the only device with a DNS value of 127.0.0.1 (because you want the server to use itself as a DNS server) - all other nodes should have their DNS value set to the server's IP address.<br />
If there is already a DHCP server providing addresses on the network that these workstations are on (and it sounds like that is the case), then I strongly recommend AGAINST setting up an additional DHCP server - it can result in mixed results (some workstations will get their address from one DHCP server, and others with get addresses from the other, and you could end up with conflicting address assignments).<br />
Just make sure that DNS is running on your server and perform the workstation test that I suggested. &nbsp;Logon and verify that you can get to internal server resources (shares, etc...) and to the internet.
</div>


<div>
mlongoh<br />
Ok, I understand not to make each workstation, 127.0.0.1, thanks for that correction.<br />
<br />
But...<br />
Lets say the server in the room &nbsp;ip address &nbsp;is 10.198.23.5, are you saying to make this ip the dns of each workstation?<br />
<br />
Also, I don't think there would be confilct with the server being a dhcp server because from the drop (source) straight to the server in the room (server is working as it own router) and the other nic &nbsp;on the server feeds a switch in the room. And addition, &nbsp;the ip network from the server &nbsp;are different from the schools network. Is this a still problem?
</div>


<div>
Yes, if the IP address of the server is 10.198.23.5, and that server is running the DNS server service, then yes, set the workstation DNS to 10.198.23.5. &nbsp;I suggest that you try it on one workstation first and verify that it works and that it improves the situation... and if so then do it to the rest. &nbsp;If it does not help then don't bother changing the other workstations.<br />
<br />
Regarding the DHCP server question... how are the workstations getting their IP addresses currently? &nbsp;And do the addresses are the workstations get on the same subnet as the server's &quot;inside&quot; NIC?
</div>


<div>
mlongoh:<br />
<br />
I will try the server ip tas a &nbsp;dns &nbsp;ip on a &nbsp;workstation to test.<br />
<br />
As for the workstation they were get ip addresses from school's network dynamicilally. But, since Friday I introduced the idea to step dhcp/ route to reimage the computers since I had to do that I felt to try the idea to use the server as a router. <br />
<br />
Yes, the workstation get the same subnet mask 255.255.255.0 as the server nic.<br />
<br />
The configuration look similar to this.<br />
<br />
Server Nic 1<br />
10.198.23.5 ( static ip in schools network)<br />
255.255.255.0 subnet mask<br />
10.198.23.1<br />
<br />
Server Nic 2<br />
&nbsp;10.0.0.10<br />
255.255.255.0<br />
10.0.0.1<br />
<br />
Should I change the subenet mask? Do you think that will make a difference not to conflict with the school's network?
</div>


<div>
No, not the subnet mask, the subnet. &nbsp;The subnet for the school's network (from your last post) is 10.198.23.0 (which &nbsp;allows addresses from 10.198.23.1 to 10.198.23.254). &nbsp;Look at the IP address of one of the workstations and tell me if it matches the IP scheme of the server's NIC2 (from your example - does it look like 10.0.0.x) or if it matches the school's network?
</div>


<div>
mlongoh:<br />
<br />
I am not sure, right now but the the workstation ips if I did it correctly should match NiC2 on the server. I tested the dhcp on the server by ghosting &nbsp;ten workstations and they saw the new network (10.0.0.0). But, I did finish to see them boot up to window.<br />
<br />
&nbsp;I only hope Tuesday when I go back the workstations will pick up the new network after booting to windows, then I can make each workstation static and try the server ip as a dns ip idea for each workstation (like you suggested earlier), change the dns suffix to the schools, and last, add workstations to the server's domain. Already created a GPO policy for the user log in like you also suggested.<br />
<br />
Finally I will test user log on and hope it satisfies the teacher because the he claims it was much faster before they moved to a new building.
</div>


<div>
Sounds good. &nbsp;The default DNS suffix should match the name of the domain, so you probably don't want to change it unless it doesn't match the active directory domain name. &nbsp;You can however add additional DNS suffixes by going into the IP properties (the same place you go to configure static IP and static DNS - click the Advanced button, click the DNS tab, where it says DNS suffix for this connection you can enter the suffix for the school's network (if it's different from the name of the active directory domain).
</div>


<div>
mlongoh:<br />
<br />
Thanks!<br />
<br />
Note: Yes, the school's dns suffix is different from the active directory. And, to make another note, in the very begin that was my problem because I tried to change the DNS and activie directory name of the the server in the room to the dns suffix &nbsp;of the schools (everything was different because the server was coming from another building). I was able to change the dns name but I gave up on the active directory name (therefore I could not change the old domain name).<br />
<br />
But the server &nbsp;seems be working fine. 
</div>


<div>
If you haven't already, change the server's DNS suffix back to the Active Directory domain name. &nbsp;Active Directory relies VERY heavily on DNS to function, so making a change like that is never a good idea. &nbsp;At best, you should add a DNS suffix, but leave that server's primary suffix the same as the domain that it is joined to (or that it is a domain controller for).
</div>


<div>
mlongoh:<br />
<br />
I am confused at your last message.<br />
<br />
Let me give you a picture of the situation pass and present. Note I am entirely sure how the school network is setup but it is connected to hundreds schools. Each school has a centralized server connected by cisco switches and routers.<br />
<br />
The centralized server no one touches besides the network administrators who are at remote locations. And they are the ones to give advice to school classroom projects like for instance the server in the room. But the key word is advice because they do not support schools doing their own server in the school because most schools do not have network administrators to support them.<br />
<br />
The advice that was given to me is in order to get the server &nbsp;in the room and workstations online (internet through schools network) for this school was to put for example a dns suffix 03X473.flasoh.org in the section control panel/system. But the on the server which came from another school had a computer name &nbsp;01X574DC01 and active directory (01X574/ Domain 01X574) plus dns server 01X574DC01.<br />
<br />
When the server was moved to the room to the new building. I thought I could change the computer name/dns server name and active directory. I was able to change the dns server name and computer name to 03X473DC01 (originally 01X574DC01). <br />
<br />
But I could not change the active directory name from the old name. &nbsp;But the workstation I tested on it logs on and is able to get on the internet &nbsp;and see the server because logon with one of the accounts that were on the server.<br />
<br />
So, stating from your last message I am not I can change the dns suffix to the active directory domain name becasue the dns suffix is what was given to me from the network administrator. And I think that dns suffix comes from the schools main server. But it is not the main dns server. The school has a dns servers (two servers) that service hundreds of schools. <br />
<br />

</div>


<div>
I think we're just having a problem understanding each other. &nbsp;I'm going to try to restate this and please let me know if I have a correct understanding.<br />
<br />
It sounds like the server in the room is an Active Directory domain controller for it's own Active Directory domain and that it is also acting as a DNS server for the Active Directory domain.<br />
In order for the workstations to join the Active Directory domain they need to be able to do DNS lookups for that domain, which is why you want them to be configured to use that server as their DNS.<br />
<br />
When the server came over to the new building, the you changed the name of the server from 01X574DC01 to 03X473DC01 and made sure that the name was udpated properly in DNS. &nbsp;The Active Directory domain name is stil 01X574 and has not changed. &nbsp;So the fully qualified name of the server is 03X473DC01.01X574.xxx (xxx is unknown to me at this point - I'm assuming that it is COM or ORG or EDU) and the NetBIOS name is 01X574\03X473DC01.<br />
<br />
I'm assuming (I'm not certain) that the workstations are currently joined to the domain 01X574.<br />
<br />
The server is also acting as a router, so all workstations have their Default Gateway set to the server's NIC2 (10.0.0.10).<br />
<br />
The school's default DNS suffix is different from the name of the Active Directory domain name, and therefore the server's and workstations have a different DNS suffix associated with their name, which should be OK.<br />
<br />
As long as you have the forwarder setup properly in the server's DNS server service, then all DNS lookups should get forwarded to the school's DNS. &nbsp;if you're not sure what the school's DNS servers are, it's most likely whatever their DHCP is assigning when it gives the workstations their addresses.<br />
<br />
It sounds like the server is routing properly if you can get to Internet from the workstations (assuming that the workstation addresses are 10.0.0.x). &nbsp;If that's the case, then it should not matter what the workstation's DNS suffix is - routing is IP based so the suffix shouldn't matter regarding Internet access, it just matters when trying to resolve IP addresses via their DNS - which shouldn't matter if you have the forwarder setup properly on the server and the workstations have the server's IP address as their DNS.<br />
<br />
That's what I understand so far. &nbsp;Please feel free to correct anything that I'm misunderstanding.
</div>


<div>
mlongoh:<br />
<br />
Thanks. Everything you said was correct besides fully qualified name of the server is 03X473DC01.03X473.flasoh.o<wbr />rg which I had changed. (03X473.flasoh.org is the dns suffix that they gave me for the school and in my ingorance when I tired to first approach this problem I tried to make DNS server, active directory/domain and the computer the name same as the dns suffix that they told me.) Not that it matter because you know more than me at this but, I was to change the computer name and dns server name ( don't remember how I did it). I could not change the name of the active directory but when &nbsp;I realized that the workstation could get internet and access the servers domain I left it alone. <br />
<br />
Does this seem ok?<br />
<br />
Tomorrow I hope the workstation will pick up the GPO Policy and now that the server is dhcp server &nbsp;(the workstation were getting ips from the schools network eventhough testing with one workstation I was able to join the domain and logon with a user), and , making each workstation static/dns point to the server's ip.<br />
<br />
I have to say, I appreciate your help because definitely if the dhcp works for this setting is very good for the teacher and the students because there are times the internet is down but now having the dhcp server the students can still work and save their files.
</div>


<div>
When you changed the DNS suffix of the server, did you do this by opening the properties to My Computer on the server, choosing the Computer Name tab and clicking the Change button? &nbsp;If so, I would change it back. &nbsp;The DNS suffix of the server should be the domain name.<br />
When you open Active Directory Users and Computers (the tool you use to add/change/delete users), the left window shows a tree structure with &quot;Active Directory Users and Computers [servername.domain] at the top. &nbsp;Beneath that is Saved Queries, and then beneath that is the domain name. &nbsp;What is the servername.domain value in the square brackets and what is the domain name listed beneath Saved Queries?
</div>


<div>
mlongoh:<br />
<br />
Wow, this sounds like a project which I thought passed.<br />
<br />
You are saying, the domain name that I see in Active Directory, I must change the (1) DNS Server, (2) Server Computer Name and (3) DNS Suffix back to it.<br />
<br />
So why did the network administrator tell me to change the dns suffix in the first place in order for the workstations/server to get online. <br />
<br />
(I figured, noticing by going to different schools that each school has a main server (including cisco routers and switches doing everything (DHCP)) and, in every school the network administrators referrs to the main room where the internet (isp/school's network) comes in as a rack. When they remote into the schools cisco routers/main server they let me know the rack number/dns suffix.<br />
<br />
And, the rack for this school, the dns suffix needed to be 03X473.flasoh.org. The former dns suffix was from a different school (different rack). When the server had all the original configurations it would not go online. <br />
<br />
Note: I understand that the server in the room should use forwarders but the dns servers are the same for all workstations and servers in all the schools and, the server did not work with it original configurations.<br />
<br />
What do you think? (I know it is difficult without being physically there but I hope I am explaining well enough) <br />
<br />

</div>


<div>
While it would be unusual from my perspective, it certainly is possible that the school's network infrastructure requires the DNS suffix of each node to be set appropriately to allow Internet access. &nbsp;If it is a requirement, I can see it being a fairly decent security/access control mechanism.<br />
<br />
It's very easy to test what's required for Internet access to function; you can do it at a workstation without changing much on the server (except for the forwarders). &nbsp;If the test workstation can get to the Internet without having the DNS suffix that matches the school's suffix (and are using the room's server for DNS), then you'll know that it is not really a requirement.<br />
<br />
Normally, any machine (server or workstation) that is a joined to an Active Directory domain has that domain's name as the suffix (ie: An AD domain called Fabrikam.com would have a workstation called COMPUTER1.FABRIKAM.COM). &nbsp;Additional suffixes can be added to each workstation to allow for proper DNS resolution if needed.<br />
<br />
Now it probably OK if the suffix is not the primary one, but frankly I've never seen an environment where the joined workstations didn't have the AD domain as their primary suffix.<br />
<br />
So, I'm not making any absolute statements regarding this, but I am recommending that you try to avoid changing the primary DNS suffix of any server or workstation that is joined to the Active Directory domain to anything other than the Active Directory domain name. &nbsp;It's absolutely necessary that the workstations are able to access the DNS server that has the AD DNS zone in it; they have to be able to reference the service records in DNS to properly find things like domain controllers.
</div>


<div>
mlongoh:<br />
<br />
Today did not go as well as I suspected.<br />
<br />
I changed everything back to the way it was before I had changed anything.<br />
<br />
I have three problems. <br />
1. Logon still slow<br />
2. I don't think the gpo policies are working.<br />
3. Although after the changes to the server, the server goes on the onlline but the workstation do not.<br />
(Note: I can't ping the server ip which I made the dns of the workstation)<br />
<br />
I notice in the dns server still has the old information from the old building. I checked 1 hour to scavenge material but it didn't work. <br />
<br />
I am stuck.
</div>


<div>
What does &quot;the server goes on the online&quot; mean? &nbsp;Does that mean that the server can access the Internet and the workstations cannot?
</div>


<div>
Yes, the server can access the internet but &nbsp;the workstation cannot.
</div>


<div>
And currently the server's DNS suffix does NOT match the school's right?
</div>


<div>
Well I noticed even when I changed the dns suffix back to old one from the former building, the server was still able to get the internet but I think it is because of the forwarders (schools dns servers). As for the workstations, yes it is not the present school's dns suffix it is the old one from the server's last school. 
</div>


<div>
OK, that confirms that you do not have to have the DNS suffix matching the school's in order to get to the Internet - you were probably told that so that DNS searches would work. &nbsp;So, at this point, you should verify that the server can get to the Internet because it is using itself for DNS queries - so check to make sure that the DNS on the server's NIC properties are pointing to itself (either it's IP addres or the 127.0.0.1 address).<br />
<br />
Once those two things are confirmed, then go to a workstation, open a command prompt and run IPCONFIG /ALL and tell me what the IP address is, the DHCP server, the DNS server(s), and the Default Gateway.
</div>


<div>
Note: I made the server in the room a dhcp server by connecting from the drop (source) (in the room) straight to the server in the room nic1 (server is working as it own router) and the other nic2 &nbsp;on the server feeds a switch in the room.<br />
<br />
Computer Name:01X574DC01.flasoh.org<wbr /><br />
DNS Name: 01X574DC01<br />
AD/Domain Name: 01X574 or 01X574.flasoh.org (Note all this was from the old school configuration, I had changed it (03X473.flasoh.org, also read at the bottom) and then changed it back to this.)<br />
Now I here am with the server having internet and the workstations not.<br />
<br />
Server Nic 1 (Server is able to get internet)<br />
10.198.23.5 ( static ip in schools network)<br />
255.255.255.0 subnet mask<br />
10.198.23.1<br />
Dns 127.0.0.1<br />
Dns servers: ( These are as Forwarders in server in room Dns Server configuration)<br />
&nbsp;10.146.23.32 <br />
&nbsp;10.146.23.33<br />
<br />
Server Nic 2<br />
&nbsp;10.0.0.10<br />
255.255.255.0<br />
10.0.0.1<br />
<br />
At workstation:<br />
<br />
For example: <br />
10.0.0.17 (by dhcp but i made static)<br />
255.255.255.0<br />
10.0.0.1<br />
Dns: 10.198.23.5<br />
<br />
<br />
I was told by school network adminstrator to put in dns suffix) School's dns suffix is 03X473.flasoh.org which provided originally server and workstation internet but slow logon for users on domain and now also I noticed gpo policies are not being pushed from the server.<br />

</div>


<div>
mlongoh:<br />
<br />
I have not heard from you. <br />
<br />
Do you have anymore suggestions?
</div>


<div>
Sorry for the delayed response... work and personal priorities. &nbsp;Two things regarding the networking:<br />
On the server NIC 2, leave the default gateway empty (there are no other routers on the 10.0.0.x network and having multiple NICs each with different default gateways can cause routing issues.<br />
<br />
Next, since the server is acting as the router for the room, change the workstation's default gateway to the server's IP address 10.0.0.10. &nbsp;This will drive any traffic going to an IP address that is not 10.0.0.x to the server and allow it to route that traffic.<br />
<br />
I make these suggestions with the understanding that there are no other routers connected to the room's network. &nbsp;You have a default gateway of 10.0.0.1 set now on the server and workstations, but I have to believe based on your description of the environment that there's no other router and nothing has that address.<br />
Try it and let me know. &nbsp;I'll be periodically checking in throughout my day today.
</div>


<div>
Thanks for replying.<br />
<br />
I made a mistake on the description of Nic2, on the server it is:<br />
<br />
10.0.0.1<br />
255.255.255.0<br />
<br />
And scope is from 10.0.0.10 to 10.0.0.100.<br />
<br />
The route seems fine but I get no internet on the workstation.
</div>


<div>
At the server, try pinging 10.146.23.32. &nbsp;If you get a response, try doing the same thing at the workstation. &nbsp;This will help to tell me if you have a routing issue or a DNS lookup issue.
</div>


<div>
10.146.23.32? <br />
<br />
10.198.23.5 is the ip of the server (Note I am making up the number if it matters to give you a clear/description &nbsp;of the issue)<br />
<br />
10.198.23.5 is the static ip that I was told I could use from the network administrator. I trying to route from that ip to the workstations. Everything seems fine besides the long logon for the users and no internet (also gpo policy are not being push to the user too). The workstation can ping itself and the server seems to be given out ip addresses also there are no ip conflicts. <br />
<br />
But I can not ping 10.198.23.5. Baffling?
</div>


<div>
10.146.23.32 is the IP address of one of the forwarders. &nbsp;I want to test that you can ping something outside of the 10.0.0.x network from the server, and then test that you can ping it from a workstation. &nbsp;If you can ping it from the workstation, then that will show that the server is routing properly and we'll most likely have a DNS lookup issue. &nbsp;If you can't ping it from the workstation (but can from the server) then that will tell me that you have a routing issue and would need to look at the RRAS configuration on the server.
</div>


<div>
Hopefully I can go to site tomorrow to double check but I think I could not ping the dns 10.146.23.32 (forwarders). I am not absolutely sure that I tried though but the ip of the server 10.198.23.5 I could not ping.<br />
<br />
If it is a route issue. What do I do? Any suggest or ideas....I had checked several times RRAS but I need help.
</div>


<div>
Well routing is the core issue that needs to work before anything else. &nbsp;So confirm that it is or is not the problem before trying to figure out how to fix it.
</div>


<div>
What if I make the server dns 10.198.32.5, the same as the ip address?
</div>


<div>
The server is accessing the Internet successfully and using itself for DNS lookups (based on what you stated previously), so making a change at the server regarding DNS will have no impact.<br />
<br />
Did you perform the ping tests from the workstation?
</div>


<div>
Just to be clear, there are 2 different DNS things going on at the server - one is the DNS client which is what allows the computer to do DNS lookups (workstations have this as well). &nbsp;When you set the DNS IP values in the NIC's IP configuration, you are identifying what DNS servers the client will perform lookups against. <br />
<br />
The server's other DNS service is the DNS Server, which is what the clients perform lookups against. &nbsp;The &quot;Forwarders&quot; is a configuration aspect ro setting of the DNS Server that identifies other DNS servers (usually Internet based servers) that your DNS Server can forward requests to when it can't resolve them itself. &nbsp;The idea is that your DNS Server knows about the hosts in the Active Directory domain, and anything else it forwards to one of the DNS servers list as a &quot;Forwarder&quot;.<br />
<br />
So, when a computer name needs to be resolved, the client service sends a lookup request to the DNS server listed as its DNS &quot;lookup&quot; server. &nbsp;The server's DNS Server service then takes that request, tries to resolve it against the zone or zone's that it has, and if it's for different zone then it sends it along to a forwarder.<br />
<br />
If a DNS client can't communicate with its designated lookup server, and you try to ping a computer by name, it will look like a communication failure. &nbsp;However, if you know the IP address of the computer your're trying to ping, you can try to ping the IP address. &nbsp;If pining by name fails but pinging by IP works, you don't have a routing issue, you have a DNS lookup issue. &nbsp;However, if pinging by IP also fails then you probably have a routing issue.
</div>


<div>
Well, I am probably going eventually take the server of dhcp because it is causing more problems than good. Before I did it add least the workstations went on the internet. The users logon was too long before the dhcp.<br />
<br />
Since the dhcp I noticed another problem. The gpo policy are not being pushed.
</div>


<div>
I'd prefer to focus on one issue at a time... once we resolve that, we can move on to the next.<br />
Try pinging the IP address of the server's NIC1 default gateway from the server and then from the workstations. &nbsp;Please let me know what the results are.
</div>


<div>
At the server, &nbsp;I had ping everything at the server were just fine, its ip address, its dns, dns forwarders, ip of the nic2 (10.0.0.1) and the workstation ip address.<br />
<br />
At the workstation, I successfully ping 10.0.0.1 (route), its own ip but I can't ping the server ip 10.198.23.5 and the server's gateway 10.198.23.1. Anything in the school's network it can not ping.<br />
<br />

</div>


<div>
That sounds like a routing problem to me. &nbsp;I'm curious to know what you can ping when you disable the DHCP service on the server and reboot a workstation and allow it to get a DHCP address from the school's DHCP server. &nbsp;Note the IP address and the default gateway of the workstation as well as what it gets assigned for DNS lookup server(s). &nbsp;You can determine the IP address information by running IPCONFIG /ALL from a command prompt.
</div>


<div>
Before I put the dhcp server on the server in the room everything ping fine. The only I had before was that the user logon took long and now I just realizing the GPO policy aren't being puch but that could have started after I put the dhcp.<br />
<br />
I won't go to the school until Monday. I don't remember as it is not the workstation doing ipconfig /all. But since the workstation could not ping the server's ip and the dns for the workstation was the ip of the server.<br />
<br />
So lets say I ipconfig /all, am I suppose to see the dns forwarders. I don't think I will see anything from the school's network. <br />
<br />
I remember I had check the RRAS nic 1 &nbsp;10.198.23.5 and nic 2 10.0.0.1. <br />
<br />
Dhcp Server scope 10.0.0.10 to 10.0.0.100.<br />
<br />
There may be a problem with the dchp (trying to remember at this moment). I think dhcp server ip was 10.0.0.10 when it should be 10.198.23.5 (right?)
</div>


<div>
IPCONFIG is just a tool that shows the workstation's IP network settings - it will show the IP address, the subnet mask, the default gateway, and the DNS lookup servers.<br />
I want to compare what the workstation's IP address, subnet mask, default gateway, and DNS server settings are now compared to after you disable the DHCP server service on the server. &nbsp;If disabling the DHCP server service allows the workstations to access the Internet, we just want to see what those settings are to have a clearer understanding of the network infrastructure, and we'll have better understanding of what we need to do to fix some, and possibly all of the issues.<br />

</div>


<div>
When I disable the dhcp and the workstation is receiving internet. <br />
<br />
Do you think it is still wise to troubleshoot the dhcp issue?<br />
<br />
I only did the dhcp server because &nbsp;I was ghosting the workstations and I had thought it would help users to logon quicker.
</div>


<div>
Minimally I want to see what the workstations have as an IP address, subnet mask, default gateway and DNS lookup IP address when the school's DHCP assigns addresses. &nbsp;It will help to understand the core problem.
</div>


<div>
I will confirm on Monday but I am pretty sure what I will see when I take off the dhcp of the server because I have seen the configuration many times also the schools pretty much have the same setup the only difference is the networks/subnet (also dns suffix) &nbsp;are different school to school. The DNS servers are the same from school to school. <br />
<br />
I am sure the configuration will be on the workstation by dhcp from the school's network be <br />
when I enter this command: &nbsp;ipconfig /all<br />
10.198.23.X<br />
255.255.255.0<br />
10.198.23.1<br />
Win 10.198.23.100<br />
Dns Servers 10.146.23.32<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.146.23.33<br />
(Don't read if there is dhcp server ip but I don't think so because dhcp is coming from the cisco routers)<br />
<br />
And without the putting in the dns suffix the workstation will not go on the internet so must put in dns suffix the network administrator told me ( 03X473.flasoh.org)
</div>


<div>
OK, I believe that I have a clearer understanding of what's happening here - we'll know for sure after you check on Monday. &nbsp;If what you describe is correct, when you disable DHCP on the server and allow the school's DHCP to assign addresses then the workstations will be on the same IP network as the server's NIC1 (instead of the 10.0.0.x subnet that NIC2 is on), which would lead me to believe that the server is not acting as a router and it's likely that the 2nd NIC may be unnecessary. &nbsp;It could be acting as an Ethernet bridge, but that will be easy to test but unplugging the server's NIC2 from the network and checking to see if workstations can still access the Internet and get an IP address assigned via DHCP.<br />
<br />
Let me know what you find on Monday.
</div>


<div>
In the interest of time, I am sure the configuration is the same as I mentioned before, what do you suggest I do after I put back everything to the way it was?<br />
<br />
Remember everything seemed fine before experimenting but the user logon taking long ( and maybe the GPO weren't being pushed but I am not sure because I noticed after I tried to route from the nic2). <br />
<br />
The teacher wants the fastest speed as possible from server to workstation (at least meaning users policies being pushed, saving files and logging on and off). <br />
<br />
Again, what do you suggest I do after I put back the network to the way it was, for agrument sake because I can &nbsp;try different solutions/ideas while I am there.
</div>


<div>
I'd disconnect NIC2 from the network and confirm that the workstations can get to the Internet. &nbsp;If they can, then we know that the server is not routing and that NIC2 is unneeded.<br />
<br />
Then, I'd disable NIC2 on the server and confirm that the server's DNS server entries are updated to reflect the server's NIC1 address.<br />
<br />
Then, I'd manually configure the DNS lookup IP address to be the address of NIC1 of the server. &nbsp;Since the server uses itself for DNS lookups and can get to the Internet successfully, the workstations should be able to do the same using the server as their DNS lookup server.<br />
<br />
You should NOT change the DNS suffix of the workstations to match the school's - it should be unnecessary as long as the workstation is using the server for DNS resolution. &nbsp;If there is a problem with accessing any school resource then set the school's DNS suffix to be a connection specific DNS suffix (set under the Advanced IP Settings for the NIC under the DNS tab).<br />
<br />
After that, I would confirm that you can access the Internet, the server, and that GPOs are being processed. &nbsp;I'd also see if the logon speed is any better.
</div>


<div>
Thats a copy. This sounds good.<br />
<br />
Just to confirm:<br />
<br />
1. I will disable nic2 on server and established dhcp from the schools network on workstation. <br />
<br />
2. On workstation, I will manually put in dns server for the workstation the ip of server in the room.<br />
<br />
<br />
I definitely think this will work.<br />
<br />
I let you know.<br />
<br />
One more thing, I am curious about the fact that the since all this time the server in the room DNS Server still has old records. <br />
<br />
What is more affective, deleting old records from the previous school manually, or go to dns server/domain properties/ advanced/ Enable automatic scavenging of stale records (to 1 hour, due time and then uncheck it)?<br />
<br />
Note: I have tried in Dns server, right clicking on domain and choosing Scavenge Stale Resource Records, that did not work. <br />
Then I tried in DNS server, right clickig on domain and choosing Set Aging/Scavenging for all Zones..., I check Scavenge stale resource records and made both options 1 hour no-refresh interval and 1 hour refresh interval ( these options are confusing because they both seem to contradict each other). Again, this did not work.<br />
<br />
What did I do wrong?<br />

</div>


<div>
Look at <a href="https://www.experts-exchange.com/questions/23139619/DNS-scavenging.html" rel="ugc">https://www.experts-exchange.com/questions/23139619/DNS-scavenging.html</a>&nbsp;and see if that helps.
</div>


<div>
Ok thanks. From what I read, deleting records is the easiest, fastest and best solution.
</div>


<div>
mlongoh:<br />
<br />
Thanks to you everything seems to be working like a charm.<br />
<br />
I did you what you said and everything working smoothlyn (internet and users logging on).<br />
<br />
Just one thing, the teacher told me that each account had map drive public and user folders, etc ( and some other I don't remember exactly). <br />
When I go to my computer we don't them.<br />
<br />
What should I do? <br />
<br />
Note the policy I created that you suggested I moved it up to second on the list of policies behind the default domain policy. I see the redirect policy (never opened it) so I assume this what were the policies for the map drives but now there not in the users profile.<br />
<br />
<br />

</div>


<div>
I'm glad you have things working properly.<br />
Regarding drive mappings... usually they are provided via a logon script. &nbsp;That script can be applied via GPO or via the user's profile, though I suggest driving it through the GPO (logon scripts and home drive mappings via the user's profile can impact performance when you have the &quot;Always wait for network&quot; GPO setting disabled.<br />
<br />
You should examine the GPOs and see if any have a logon script, and try to find that script and determine why it's not being applied.
</div>


<div>
Did you get things working completely? &nbsp;If so, can you accept an answer and close this question?
</div>


<div>
mlongoh,<br />
<br />
I need more help. &nbsp;( I thought I would be finished) I have trouble with the GPOs <br />
<br />
You mentioned the GPO setting &quot;Always wait for network&quot; should be disabled which it is now but, it can affect profiles.<br />
<br />
The redirect (offline sychronization) is not working properly. When user logs off the backup does not complete due to error. In the GPO, I don't see how the redirect folders settings. Is there a way to clarify this?<br />
<br />
Also, in the StudentGPO ( is the only one that has a setting that I can see for active desktop/background), I have difficulty change the background for the student users. I put a picture in the same folder that is in the StudentGPO and that did not work. Then I added a simply batch file that normally works for me in StudentGPO (logon scripts) which is &nbsp;copy \\01X574DC01\PUBLIC\pic.bm<wbr />p c: and this does not work either. In the pass, I tried vbs scripts for desktop background but they never worked for me. I think the problem here that is different the user logon profiles excludes the c drive and only shows mapnetwork drives. What do you think?<br />
<br />
<br />
Note there were GPO policies on this server before. I did not want to trouble the original settings. When I right click on the domain and go to policies I see the list of GPOs starting from default domain policy then created ones.<br />
The names of the GPOs explain what they are for like RedirectGPO, StudentGPO and &nbsp;InternetGPO but when I check them I do not see any logon scripts, vbs scripts or how they are being performed besides what I see in the StudentGPO. And because I was not sure out of frustration (ha!) I started putting logon scripts for the desktop and network mapdrive (because all the drives where not show at first according to the teacher) in the StudentOU and TeacherOU.<br />
<br />

</div>


<div>
The GPO handles redirection via GPO settings rather scripts - which I personally hate because of the errors you are seeing. &nbsp;However, the path of least resistance would be to Enable Always Wait for the Network at Startup and Logon - it will slow things down a bit but you won't have your errors, and that setting may not have been the source of your speed problems - it was more likely the length of time it took to locate the domain and logon because of your DNS woes, so it probably will be OK.<br />
<br />
I personally prefer to simply redirect the user's My Documents to the user's &quot;home drive&quot; by updating the registry key and not using the built in GPO to do it. &nbsp;It's a personal preference and not always the best approach - certainly not good when you have laptops in the environment that aren't always connected to the server. &nbsp;It's also a little more complicated to get setup.<br />
<br />
Regarding your background bitmap issue, we're already discussing it in the other question that you posted - which is good because I was going to recommend posting it as a new question.
</div>


<div>
Are you saying the option originally to help the logon speed &nbsp;&quot;Always wait for the Network&quot;, now to &quot;Enable&quot; it instead of having it &quot;Disabled&quot;.<br />
<br />
I would love for the other option for the registry key instead of GPO but the teacher wants to implement laptops in the future.
</div>


<div>
I also posted question on redirect &nbsp;GPO....
</div>


<div>
<div class="content wysiwyg-content">
How can I make clients log on faster to server?
</div>
</div>


How can I make clients log on faster to server?

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).