syswow64 blog

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 --valsetuppwd=PASSWORD cc

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