- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) / Re: Detection methods for Applications use hardcoded paths instead of environment variables
January 31, 2020, 09:10:56 AM #2
Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) / Detection methods for Applications use hardcoded paths instead of environment variables
January 31, 2020, 08:42:41 AM
Hi folks - thanks for everything. Got PmPC up and running in our environment and we are in the process of getting things going for ourselves. One item of concern that came up:
While unlikely, it's possible that Windows installations are not installed to C. Paths for Windows\Temp and CCM\Logs in the Detection methods of applications are hardcoded for an installation directory of C:\Windows\. Would it be possible to move to environment variables such as $env:WinDir, $env:temp, and $env:systemdrive for example, for greater compatibility and flexibility?
Thanks.
While unlikely, it's possible that Windows installations are not installed to C. Paths for Windows\Temp and CCM\Logs in the Detection methods of applications are hardcoded for an installation directory of C:\Windows\. Would it be possible to move to environment variables such as $env:WinDir, $env:temp, and $env:systemdrive for example, for greater compatibility and flexibility?
Thanks.
Pages1