Sage 100

I think to get much help you'll need to be more specific about what exact errors are occurring. In my experience with locked down permissions - it can be a long long process

Here Is what's helped for me:

• connect with IT and have THEM using their elevated permissions try to get it running. Use MAS90 Mode or run as an app while logged in with THEIR elevated permissions. 
  
  
• the key is to find an IT resource who can work 1:1 with you on this debugging. You will need to make at least one friend on the IT staff. If this customer is like mine - I had to wade through 12 different IT people and find the one who dealt with desktop config and usually also the Network (server) admin. These are all segmented so no one IT person has full admin access. 
• with VDI I believe my customer's IT had to give SI users a static machine name otherwise there were problems after the user logged out and back in. 
  
  

I'm sure you are aware of this - most VDI type environments won't save anything that's installed once you reboot. Unless the admin installs to the image there's no (practical) way for a user to install anything and have it persist for their next reboot/login. 

Good recap.  We have been working on this for two weeks now.  My SI guy has been doing SI for 10 years and he is stymied.  We have followed many (if not all) Sage KB's on the topic.  Numerous people in IT.  We have installed using their admin credentials, still getting weird errors.  We have completely uninstalled the Sage client following the Sage  KB instructions.  We can't even get it to run on a local workstation.  We brought Sage in and they basically punted.  

I think to get much help you'll need to be more specific about what exact errors are occurring. In my experience with locked down permissions - it can be a long long process

Here Is what's helped for me:

• connect with IT and have THEM using their elevated permissions try to get it running. Use MAS90 Mode or run as an app while logged in with THEIR elevated permissions. 
  
  
• the key is to find an IT resource who can work 1:1 with you on this debugging. You will need to make at least one friend on the IT staff. If this customer is like mine - I had to wade through 12 different IT people and find the one who dealt with desktop config and usually also the Network (server) admin. These are all segmented so no one IT person has full admin access. 
• with VDI I believe my customer's IT had to give SI users a static machine name otherwise there were problems after the user logged out and back in. 
  
  

I'm sure you are aware of this - most VDI type environments won't save anything that's installed once you reboot. Unless the admin installs to the image there's no (practical) way for a user to install anything and have it persist for their next reboot/login. 

Good recap.  We have been working on this for two weeks now.  My SI guy has been doing SI for 10 years and he is stymied.  We have followed many (if not all) Sage KB's on the topic.  Numerous people in IT.  We have installed using their admin credentials, still getting weird errors.  We have completely uninstalled the Sage client following the Sage  KB instructions.  We can't even get it to run on a local workstation.  We brought Sage in and they basically punted.  

I think to get much help you'll need to be more specific about what exact errors are occurring. In my experience with locked down permissions - it can be a long long process

Here Is what's helped for me:

• connect with IT and have THEM using their elevated permissions try to get it running. Use MAS90 Mode or run as an app while logged in with THEIR elevated permissions. 
  
  
• the key is to find an IT resource who can work 1:1 with you on this debugging. You will need to make at least one friend on the IT staff. If this customer is like mine - I had to wade through 12 different IT people and find the one who dealt with desktop config and usually also the Network (server) admin. These are all segmented so no one IT person has full admin access. 
• with VDI I believe my customer's IT had to give SI users a static machine name otherwise there were problems after the user logged out and back in. 
  
  

I'm sure you are aware of this - most VDI type environments won't save anything that's installed once you reboot. Unless the admin installs to the image there's no (practical) way for a user to install anything and have it persist for their next reboot/login. 

@Jeff Schwenk  What's the exact error message?  When you installed Sage 100 workstation setup and then re-installed, did you tun off user access control?  I have a customer whose IT department "loves" to do the workstation install on new computers.  I received a call about the owners new laptop that couldn't run SI.  They had uninstalled and re-installed several times.  They thought I was a magician when SI worked after I turned off UAC first then uninstalled and re-installed workstation setup.

Good recap.  We have been working on this for two weeks now.  My SI guy has been doing SI for 10 years and he is stymied.  We have followed many (if not all) Sage KB's on the topic.  Numerous people in IT.  We have installed using their admin credentials, still getting weird errors.  We have completely uninstalled the Sage client following the Sage  KB instructions.  We can't even get it to run on a local workstation.  We brought Sage in and they basically punted.  

I think to get much help you'll need to be more specific about what exact errors are occurring. In my experience with locked down permissions - it can be a long long process

Here Is what's helped for me:

• connect with IT and have THEM using their elevated permissions try to get it running. Use MAS90 Mode or run as an app while logged in with THEIR elevated permissions. 
  
  
• the key is to find an IT resource who can work 1:1 with you on this debugging. You will need to make at least one friend on the IT staff. If this customer is like mine - I had to wade through 12 different IT people and find the one who dealt with desktop config and usually also the Network (server) admin. These are all segmented so no one IT person has full admin access. 
• with VDI I believe my customer's IT had to give SI users a static machine name otherwise there were problems after the user logged out and back in. 
  
  

I'm sure you are aware of this - most VDI type environments won't save anything that's installed once you reboot. Unless the admin installs to the image there's no (practical) way for a user to install anything and have it persist for their next reboot/login.