IT Employment

Ask something
Discussion Locked

Slow login Script

0 helpful
7 replies

by jkeeley

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have some strange problems with my login scripts (NT Domain). Some machines process these scripts quickly, while others are very slow. All machines are configured the same. The locations don't seem to make a difference either (we are spread over large area), the machine right next to my office runs slow while mine runs fast.

Any ideas?

Thanks in advance...

-JK

7 replies

by goshevan

We had a similar problem not long ago. It seems that NT stores user profiles, including internet histories, which can create rather large files after a long day of work. I believe there is a way to dump these automatically and allow a faster log on(no waiting for the profile to load) and take up less space on the server. These histories tend not to be useful info, but rather clutter that slows everything down.

by lloyd

SPEED UP THAT START MENU
You can control the speed of navigation on the Start menu by tweaking a

registry setting. This change reduces the time it takes for the Start

menu to display the next tree when you move your cursor over it. To

make the change, follow these steps:

1. Type regedt32 at the run command (Start | Run).

2. Navigate to HKEY_CURRENT_USER/Control Panel/Desktop and select

MenuShowDelay.

3. Change the value of this setting to 100 and click OK.

4. Exit the Registry Editor and restart your system.

by lloyd

previous is after in nt. really you looking at services starting or the local persons logon script, is your logon as slow as your colleague's?

there is also another way but...

ENABLING AUTOMATIC LOGONS
Although it does seem to go against basic security rules, there are

some situations when you might need to set up an NT machine to log on

automatically, completely bypassing the standard logon sequence. This

might be necessary for a remote print server or other specialized

application server, for example. The following registry edit is

required for automatic logon.

1. Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE
SOFTWARE\ Microsoft\Windows NT\CurrentVersion\Winlogon.

2. Determine which user account to use for the automatic logon and then

change the value of DefaultUserName to the desired user account name.

3. Add a new value entry called AutoAdminLogon. Set its data type to

REG_SZ and its value to 1.

4. Add another new value entry called DefaultPassword. Set its data

type to REG_SZ and its value to the password of the account specified

in step 2.

When you log off, NT automatically logs on the user that you specified

in step 2. Whenever anyone logs off this computer, NT logs the default

user on again. If you want to revert to requiring a normal logon,

change the AutoAdminLogon value entry that you created in step 3 to a

value of 0.

by chad_story

I think that it could be a number of things. Run a perfmeter on the at least 2 machines (One that process the script in quickly, then one that lags a little) I have found that on some of my workstations, and even servers, that that the read/write times on different machines differ. Also, at logon, some machines may be loading different applications at startup that will eat up CPU which in turn will slow down the reading of the script where as some machines may not load these processes on start up.

by bklein

I'm leaning toward the idea that the problem is actually with discovery throughout the network. The workstations just hang there for a minute, and will occassionally return a message that it can't find a domain controller and logs on with cached information.

I see similar behavior when workstations attempt to save file to the FS. Also same "hangy" behavior when launch "network neighborhood."

All workstations and servers are NTFS. Let me know what you find out!

Bob

by edwardscs

Slow login Script
Are you assigning the correct DNS's or are they done by a common DHCP server? Check to make sure these are correct. One client used the gateway address (10.0.1.1), not the Win2K Server (10.0.1.10) and we saw these results. Hope it helps.

Neil

by edwardscs

Are you assigning the correct DNS's or are they done by a common DHCP server? Check to make sure these are correct. One client used the gateway address (10.0.1.1), not the Win2K Server (10.0.1.10) and we saw these results. Hope it helps.

Neil

This discussion is closed to new replies.