Slow windows log on after Essentials Install
I have an odd server issue. What started as a small delay now takes about 15 minutes to get to the server desktop after I enter my network credentials. We were not sure what was causing it. After a lot of troubleshooting we decided to stand up a new VM. The slow logon is no longer an issue (under 10 seconds) after installing ArcGIS Server and some other apps. I then installed Essentials 4.5.1 & GVH 2.6.1 and the slow log on issue has resurfaced at 1.5 minutes to desktop. I reverted to my pre Essentials snapshot and no issue. Reinstalled essentials and slow logon again. Win 2012 R2.
I did a typical/full install, changed install drive letter from C to another, set windows log in (tested default builtin/admins as well as domain admin group), configured two FQDN hosts, and let the installer create the default app pool accounts all on the default website.
Any thoughts or recommendations?
Thanks,
Lee
0
-
We have been having a similar issue. Login times around 19 minutes. We tracked it down to the group policy taking forever to process once Essentials 4.4.2 was installed. By disabling the service it was back to normal login times. My system admin used http://sysprosoft.com/policyreporter.shtml to locate the issues but still dont have a solution. Was thinking of going to the current version but looks like you are on it so im guessing that wont solve the issue for us.
Maybe we need a programmer at Latitude to do a trace?
Greg Beard0 -
Hi Greg,
There are a couple of things you can check:
1) Is ArcGIS server installed on the same server as Essentials? if so, do you see the same slow logins if you disable the ArcGIS server service?
2) How much RAM do you have? Are you close to hitting the limit?
3) If possible, can you clone your production server, and try uninstalling the current version of Essentials, and installing the 4.6 beta? Our developers think that this may help customers that are experiencing slow login issues.
If you have any followup questions, please let me know, or open a support case, so one of the analysts can take a look :)
Cheers!
Danny0 -
Hi Greg,
If possible, can you please also send me some details about the GPO that is processing for so long? If you don't want to post it here, you can email me (dbriggs@latitudegeo.com)
Thanks!
Danny0 -
Thanks for helping Daniel! I dont have any issues posting it here as it may help others :)
1 - Tonight after hours we will try and enable the Essentials and disable the ArcServer services to see how the speed is affected.
2 - Currently we have 16GB of ram on that VM and running at 44% with Essentials dissabled.
3 - We could give the beta a try if you think it may fix it. Is it available in the downloads area? 4 - About the GPO my system admin says 'it's impacting multiple GPO's and even stuff ranging from simple drive mapping to setting security policies.'0 -
Thanks for the reply Greg, please let me know how it goes tonight!
To sign up for the beta, you'll want to reach out to your account manager, he'll be able to sign you up and provide you with the download link.
Cheers!
Danny0 -
Did some testing last night on the server. With ArcServer off and Essentials on the logon was still fast. That makes it look like the conflict is between the two packages. I requested the Beta and will try it out soon.
Greg Beard0 -
Hi Greg,
Thanks for the update, please let me know how it goes!
Thanks,
Danny0 -
Posting these results is long overdue. Just wanted to confirm here that upgrading to the latest version of Essentials and GVH resolved my issues. Thanks. 0 -
Glad to see that we weren't the only ones who had experienced these issues. We were pulling our hair out trying to determine what the issue was, and dreaded anytime that we had to log into that server because it would take forever, and then *poof* it went away one day when the Geocortex Core service had stopped running on our server, and that's when we were able to determine the issue.
Subsequent to upgrading to the new version, we no longer have any issues.
BC0 -
I'm using the latest version of Geocortex and HTML5 viewer and it's taking upwards of 40 minutes to login to the server. Looks like this issue has come back with a vengeance. 0 -
Hi Joshua,
I'd recommend opening a case with our (To: support@geocortex.com) technical support team so they can take a look.0 -
I figured it out. Turning on FIPS Cryptographic Modules in the server's policy fixed it. Turning FIPS on forces Geocortex Core into using standard SSL when validating the service on login.
You might want to pass this on to your dev group for future reference. It took my login time down from 40 minutes to less than 2 seconds.0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
12 kommentarer