tag:blogger.com,1999:blog-268736241887032504.post7050403727877069394..comments2010-05-20T12:49:00.657-07:00Jivtesh Singhhttp://www.blogger.com/profile/09314498953058276237noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-268736241887032504.post-86288272766400088822010-05-20T12:49:00.650-07:002010-05-20T12:49:00.650-07:00I had this issue where the users were in one city/domain and the terminal server was in another city/domain.<br /><br />The issue was caused by a mapped drive auto-started by the system policies (so ALL users could share in a common Accounting file share).<br /><br />The users in City B/Domain B had LONG log-in times. Solution was to create NEW GP-ONLY log-in ID&#39;s to the terminal server where the Policy did not auto-set the mapped drive.<br /><br />GP creates some type of directory on a server in Domain B that then GP tries to constantly update (or something like that). If someone has this issue I can probably dig into my notes and help.<br /><br />Mike Lupro - MikeLupro@BestTechsNW.comMike Luprohttp://www.blogger.com/profile/02572277607789775753noreply@blogger.comtag:blogger.com,1999:blog-268736241887032504.post-5158821865359506492007-11-29T05:41:00.000-08:002007-11-29T05:41:00.000-08:00I had a number of workstations (XP, Win2k) on an AD network which took more then 10 minutes to get to the login screen... tried all the suggestions above and then some. Once logged in GP 9 is fast, no other issues.<BR/>The solution for me was to delete the affected user profiles. Once this was done all the login screen appear in 2 to 5 seconds. With saving/restoring the profile directories of my documents, favorites, desktop,and start menu, took approx. 30 minutes per machine.Paul Meinersnoreply@blogger.comtag:blogger.com,1999:blog-268736241887032504.post-71782458993728830472007-10-31T13:57:00.000-07:002007-10-31T13:57:00.000-07:00I have a similar issue. I was running GP v8 on a SQL2000 server. I upgraded to v9 and also moved to a SQL2005 64-bit server. All the ODBC connections to the server run much slower. I have connections from numerous applications besides MS Access. The SQL2005 64-bit is on a W2003 64-bit server with 4 CPU's and 8gb memory. Plenty of hard disk space and only 15-users. I am not sure where to look for help. I sent ODBC traces to MS when we first converted and they saw nothing.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-268736241887032504.post-36305135629253360832007-10-31T07:30:00.000-07:002007-10-31T07:30:00.000-07:00CP,<BR/><BR/>Glad i was of help! Take care!<BR/><BR/>JivteshJivtesh Singhhttp://www.blogger.com/profile/09314498953058276237noreply@blogger.comtag:blogger.com,1999:blog-268736241887032504.post-13428423377737761032007-10-31T06:52:00.000-07:002007-10-31T06:52:00.000-07:00Hi Jivtesh ,<BR/><BR/>Its a great help for me to resolve the login delay. I installed the latest GP service pack and login time was reduced drastically.<BR/><BR/>Thank you.<BR/>CPDinesh@gmail.com..::വഴിപോക്കന്‍[Vazhipokkan]http://www.blogger.com/profile/13895879472231863037noreply@blogger.com