<div>
That is generally either a Group policy driven thing, or a profile driven thing. &nbsp;GPO could be installing software, or mapping drives or printers that are now not available or some other issue applying one or more policies. &nbsp;The user's profile may be corrupt or have other issues (are they roaming profiles on here?)
</div>


That is generally either a Group policy driven thing, or a profile driven thing.  GPO could be installing software, or mapping drives or printers that are now not available or some other issue applying one or more policies.  The user's profile may be corrupt or have other issues (are they roaming profiles on here?)

<div>
We tried a new profile and it made no difference. It turned out to be a DNS issue. We deleted the fixed DNS entry and then cleared all the cache and re-entered the local IP of the local DNS server. This cured it immediately.
</div>


We tried a new profile and it made no difference. It turned out to be a DNS issue. We deleted the fixed DNS entry and then cleared all the cache and re-entered the local IP of the local DNS server. This cured it immediately.

<div>
I've requested that this question be closed as follows:<br />
<br />
Accepted answer: 0 points for JayHine's comment <a href="https://www.experts-exchange.com/questions/28490975/Server-2003-takes-2-3-minutes-to-apply-personal-settings-when-logging-on.html?anchorAnswerId=40298489#a40298489" rel="ugc">#a40298489</a><br />
<br />
for the following reason:<br />
<br />
We solved it by resetting the DNS entry
</div>


I've requested that this question be closed as follows:

Accepted answer: 0 points for JayHine's comment #a40298489 [https://www.experts-exchange.com/questions/28490975/Server-2003-takes-2-3-minutes-to-apply-personal-settings-when-logging-on.html?anchorAnswerId=40298489#a40298489]

for the following reason:

We solved it by resetting the DNS entry

<div>
It was the DNS settings on the Terminal Server which were causing the problem.
</div>


It was the DNS settings on the Terminal Server which were causing the problem.

<div>
<div class="content wysiwyg-content">
Hi, <br />
<br />
We have aServer 2003 running as a Terminal server. For the past week it takes between 2 to 3 miutes to login. It stays on &quot;Applying personal settings&quot; for most of the time.<br />
<br />
They never had this problem though. <br />
<br />
Any ideas to why it takes so long to logon?!?
</div>
</div>


Hi, 

We have aServer 2003 running as a Terminal server. For the past week it takes between 2 to 3 miutes to login. It stays on "Applying personal settings" for most of the time.

They never had this problem though. 

Any ideas to why it takes so long to logon?!?

Server 2003 takes 2-3 minutes to &quot;apply personal settings&quot; when logging on.

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).

Server 2003 takes 2-3 minutes to &quot;apply personal settings&quot; when logging on.

Server 2003 takes 2-3 minutes to "apply personal settings" when logging on.