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...

Office 365 Update Restarts my Apps in SCCM Pushing Office 365 C2R updates through SCCM 1610 causes Office applications to close unexpectedly on client PCs This is a known bug since the release of ConfigMgr CB 1610. and was resolved with Hotfix KB4010155 https://support.microsoft.com/en-us/help/4010155/update-rollup-for-system-center-configuration-manager-current-branch-v  After you start installation of Office updates from Software Center, users do not receive a notification message to exit all open Office 365 applications. This behavior occurs even with the  forceappshutdown=False  switch in the Configuration.xml file for Office 365. Conclusion Install all hotfixes https://support.microsoft.com/help/4010155 https://support.microsoft.com/help/4016483

Dell E5450 Bricked after applying CCTK.exe command Dell E5450 with i3 Processors a CCTK.exe warning We recently had our E5450 Latitude failing to post following a stand SCCM Window Task Sequence.  It was collected for diagnosis and motherboard swap out.  While no diagnosis was performed (pointless sending away) we was returned within a few days with a new motherboard. Upon receiving it I cautiously rebuilt it with success with a cut down version of the task sequence; I have simply installed the Windows Image (WIM) and driver package.  Upon introducing additional steps to the SCCM task sequence I see a complete failure of the BIOS as previously experienced. The failed post was the result of CCTK.EXE modifying BIOS settings. We are using the latest version of CCTK 3.2 with the following commands;  cctk --secureboot=enable --valsetuppwd=PASSWORD cctk --wakeonlan=enable --valsetuppwd=PASSWORD cctk --uefinwstack=enable --valsetuppwd=PASSWORD cctk --embsataraid=ahci --vals...

Sharepoint documents will not open in Word/Excel Today I have been dealing with a very interesting Office 365 / SharePoint issue. It was reported that the Edit in Application button within SharePoint i.e. “Edit in Excel” “Edit in Word” is not working correctly and results in an empty Spreadsheet or empty Word document. Viewing and Editing within the browser is fully functional and the behaviour varies depending on computers within specific OU in active directory.  It is worth noting at this point the estate consisted of Office 2013 ProPlus installations running on Windows 8.1. The fact that identical systems with identical software versions patch to the same level, resulted in different behaviour could only mean Group Policy was different between them. I was quickly able to find the offending policy; " Block signing into Office: Enabled ". The screen shot above details a systems policy with the issue. With the Standard Workstation GPO's the policy "Block signing into...