Archive for May, 2011


 

this is more for reference but if you want to know what versions of exchange and office will work with and what functionality it will have check the technet link below!

Enjoy

http://technet.microsoft.com/en-us/library/gg412817.aspx

This was an interesting process to me and after years of working in IT you forget about how much actually happens behind the screens… and when you sitting there watching loading profile etc..

So first of all sometimes it can be very easy check the basics….

1. check the network and ensure there is nothing going on

2. check your domain controller ensure that is not over loaded and is processing requests quickly

3. check the machine you are on and see if it is slow anyway over all….

 

these are all fairly standard stuff to check… task manager will help you understand if your system is performing badly, if you are more advanced the perfmon and if you want to get more advanced well.. Smile

First thing you need to do is start here –> http://blogs.technet.com/b/askds/archive/2008/11/11/understanding-how-to-read-a-userenv-log-part-1.aspx

This will show you how to turn on USERENV logging and how to read the file…

This is a great place to start… you can examine the trace and figure out what parts are taking ages…

a quick tip is in the userenv.log that will be created search for a string of lpuser

lpuser signifies a logon attempt … trace the log down from there until you see that the group policies applied successfully… this will give you great insight into the log on process…

after this you need to look at the file from the point of the group policies applying successfull to the point of explorer.exe (this is when they should see the desktop) and work thru the log at see what parts are taking alot of time to launch and run…

 

Additionally if you are like to get even more detail… download sysinternals suite and run procmon…

Click options and boot logging in procmon and reboot the machine and repeat the process…

this will give you another wealth of information that you can match up with the userenv log and see what process is possible causing the system to be slow

if it doesnt turn out to be any of this… then very simply using netmon or wireshark… on a laptop … plug the affected PC and the laptop into a hub and then the hub into the wall port or switch (sometimes you might need a network cable) and capture the trace of the the machine logging… what the streams and focus on any major delays in a response for different parts of the logon process…

 

this is not easy stuff sometime and can require a lot of time to troubleshoot but you will really begin to understand the depth of whats goes on during that little process…

I came across this one which i taught was very interesting….

 

basically an app logs on and uses a sql express database for whatever reason… well lets say the user leaves their desk and returns 15 minutes later… which is a common enough experience. They log back on to the app and they notice a timeout on the app or very slow to initially respond.

 

well this could be cause be sql express after about 10 mins it will close database connections and flush its cache…. if you want dont want this problem your app has to be programmed to work in the background to query a db every couple of minutes, doesnt have to do anything specific but just run a simply read query against the database… and then should fix it!

interesting little problems…

i am taking a longer break than expected from blogging etc.. but will return in a few weeks… try to get a handle on my new job!