This project has moved and is read-only. For the latest updates, please go here.
1

Resolved

Slow Launch (Not Responding)

description

Current Version: 1.0.2.2
Assembly Version: 1.0.2.18810

Hi Roger

I can confirm we are experiencing the same as Id #1665 too.

For the last four opens on my machine, the UI does not appear until 18 seconds and then '(Not responding)' until 50 seconds.

Is this due to the version check/dialing home?

Running Client Center as an administrator, inhibits internet access in our environment - and most other enterprises these days if they have any worthwhile security in place). Proxy does not allow admins.

This renders CC inoperable until the version check times out, as that is not a background process.

If so, could you make that a background process, to completely eliminate this delay?

comments

rzander wrote Mar 1, 2016 at 3:51 PM

You can disable the Self-Update check by removing the File "Plugin_SelfUpdate.dll"... Does it start faster without Self-Update check ?

rzander wrote Mar 8, 2016 at 6:51 PM

Just checked in current Version (1.0.2.10), the plugins are loaded in a background task. Self-Update is also a plugin so it should not affect the startup time...

I can not reproduce the Issue but I've seen it on a Demo @MMS.

I think it has something to do with the code signing certificate. But I need some input from someone who can reproduce the behavior...

Questions:
1) Are your Root CA's up to date... (there is a WindowsUpdate that updates the Root CA's)
2) Have you enforced CRL (Certificate Revocation List) checking (think it's an IE Policy)
3) Is "StarCom Certification Authority" a trusted ROOT CA (or check the signing cert of SCCMCliCtrWPF.exe)
4) What is the PowerShell, OS and .NET Version
5) Can you reproduce the Issue when you start the Tool with
    - a local Account
    - a Workgroup machine (no GPO's or other security Settings)
6) Does it startup faster, when all plugins are removed

wrote Mar 8, 2016 at 6:52 PM

rzander wrote Jan 4 at 8:29 AM

Set the status of this issue to resolved as the problem is caused from the OS and the OS configuration.

wrote Thu at 5:54 PM