Project Server Cache Does Not "Stick" in Virtual Windows 10 Environment RRS feed

  • Question

  • I am part of a pilot Windows 10 test team prior to the deployment of the operating system to the rest of the customer environment.  The IT department (different contractor) uses a virtualizer to allow us to obtain the Project Pro v2013 client wherever we logon within the Customer's system.  Everybody uses thin clients. 

    At first the Windows 10 environment seemed okay, but I have since noticed that each morning when I logon I have to go into the configure accounts popup to re-add the URL for our Project Server and then go into Options>Save to re-add the location of the cache and update the cache limit. 

    Annoying.  Our users are going to scream if this is not fixed by the time they are migrated to Windows 10.  I have forwarded details to the IT contractor, but as of yet I have not received feedback as to the root cause or a fix.


    Chris Sobolewski

    Monday, January 22, 2018 10:23 PM


All replies