syswow64 blog

SCCM Task Sequence with App-V application " A supported App-V 5X client is not installed" Scenario: Windows 10 (1607) Task Sequence with various MSI and App-V applications. During an SCCM Task Sequence I am attempting to install an App-V application however, at the end of the build MSI installations have installed but App-V application has not been installed. AppDiscovery.log    Performing detection of app deployment type MathWorks_MATLAB-R2014a_8.3.0.532_001A - Download..... +++ App-V 5X application not discovered. A supported App-V 5X client is not installed. Resolution: With Windows 10, version 1607, the App-V client is installed automatically however, it needs to be enabled before you can installations App-V packaged within a Task Sequence.  This can be achieved by adding a command line to you Task Sequence to run Windows PowerShell command. powershell -executionpolicy bypass -command Enable-Appv

Scenario : On the root of the C drive you right click and select New "Folder".  Windows will then create 4 New folder i.e. New Folder, New Folder (2), New Folder (3), New Folder (4).  To delete or open these folders you need to elevate permissions on each one. We have seen this issue only occur on Windows 10 systems applying Group Policy. Cause: In our environment a specific Group policy was filtered to Windows 10 only.  Within this policy the following security setting was set to modify C: drive file permissions: Computer> Policies> Windows Settings>File System The policy specifically was allowing Administrators Full Control and Users Read and Execute permissions to " This Folder" only .  This had the affect of preventing sub-folders from  inheriting Administrator / Users permissions. If this policy does not exist or is set to "This folder, Sub-folders, and files" then the additional Folders are not created. I believe this issue is a bug in the w

Scenario : On the root of the C drive you right click and select New "Folder".  Windows will then create 4 New folder i.e. New Folder, New Folder (2), New Folder (3), New Folder (4).  To delete or open these folders you need to elevate permissions on each one. We have seen this issue only occur on Windows 10 systems applying Group Policy. Cause: In our environment a specific Group policy was filtered to Windows 10 only.  Within this policy the following security setting was set to modify C: drive file permissions: Computer> Policies> Windows Settings>File System The policy specifically was allowing Administrators Full Control and Users Read and Execute permissions to " This Folder" only .  This had the affect of preventing sub-folders from  inheriting Administrator / Users permissions. If this policy does not exist or is set to "This folder, Sub-folders, and files" then the additional Folders are not created. I believe thi

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys