Super Long timeout for "INFO: Checking status of SharedAccess..." during setup/upgrade
Every time we do a ConfigMgr installation or upgrade - even now with in-console updates - there's a ridiculously long wait (105 minutes) when the setup tries to verify that the SharedAccess service has been restarted. Two problems: 1) the timeout is way too long; don't know how this is even calculated but in our much smaller lab environment it's only 7 minutes, and 2) the service is disabled so why are you even trying to start it in the first place????
This causes our site server upgrades to take much longer than they need to and introduces extended outages of ConfigMgr - a key Production application. Can this be fixed? Either adjust the timeout algorithm to have a reasonable maximum or simply don't even try to start a disabled service (or both!).