Sam's IT Knowledgebase

Recently I was working on a project to migrate the organisation from Office 2010 to Office 2016 (365). After the upgrade we had some finance staff complaining that since the update Excel would take a long time to close. It was hard to narrow down the exact cause of this as there was also an update of Jet Reports at the same time. After a bit of investigating I recreated a users local profile which seemed to fix the issue. After doing this I compared the App Data\Roaming\Jet Reports\settings.xml file and compared the differences and noticed an interesting line of code as below <setting name="SendUsageStatistics" type="Boolean" encrypted="false">     <value> True </value> I then tested changing the send usage statistics value to false, closed Excel, reopened and now it works fine.

To be compliant and allow Windows 10 Branching Updates to 1803, the SCCM console needs to be updated to the latest version, which is 1806. This is available as an in console update, providing that you are currently on one of the Current Branch Console Versions. To see the support tree see the following link from Microsoft - https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10 The current support timeline is as below Windows 10 version Configuration Manager 1706 Configuration Manager 1710 Configuration Manager 1802 Configuration Manager 1806 Enterprise 2015 LTSB Enterprise 2016 LTSB 1607 ( see editions )   1   1   1   1 1703 ( see editions ) 1709 ( see editions ) 1803 ( see editions ) The first step in doing this is to update to ADK. If you do not do this prior then you will need to do this after the console update, which is a lot longer process. For details on how to do this then follow this guide from System...

So in my current project I am working on deploying Office 365 in our Organisation. I had an issue in the early stages of testing where some users would get a pop up box (as below) asking for their credentials to activate the product. While this was not a showstopper, we did not want this coming up for every user once we go live with the rollout to over 1300 staff members. There were a few factors which caused this to happen and the fixes below. I was under the impression we were running Active Directory Federation Services. After speaking to one of the System Admins I found out we were actually running Seamless Single Sign On instead. To prevent this from coming up there were a couple of steps which I had to do. For Windows 10 systems it automatically supports AD SSO. For Windows 7 and 8.1 devices I had to install an extra piece of Software called Microsoft Workplace join for non Windows 10 computers here - https://www.microsoft.com/en-us/download/details.aspx?id=53554 On...

I recently had an issue where I am working on an Office 365 rollout and in the early stages of the pilot group I came across a user which was not showing in Azure, and thus missing from the Office Online Portal. I ran the IDfix utility which brought up no issues with the specific user. After engaging with Microsoft it was determined that an attribute in the AD object of this user was different to most other users and the query which Azure runs conflicted with this attribute. In our situation it was the msExchRecipientTypeDetails which was set to 2 for this particular user, and the Azure query we had filtered on only allowing if this was set to 1.

I am currently working on a project to implement Office 365. In the organisation I work for there is a mix of 2010 and 2013 installs. I came across a bit of an issue when Visio would not install. The first step is in your install directory - \\server\share\vispro.ww create an install XML file. The contents of the file I used were as follows: <Configuration Product="ProPlus">  <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />     <Logging Type="standard" Path="C:\Install\Logs" Template="Microsoft Office Visio Standard Setup(*).log" />    <Setting Id="SETUP_REBOOT" Value="NEVER" /> </Configuration> I then created a batch file to uninstall with the following syntax: \\server\source\setup.exe /uninstall Visio /config "\\server\source\vispro.ww\uninstall.xml" I was getting some errors on the log file as ...

I recently came across an issue where a user was suddenly unable to browse through the network places / network discovery in Windows 10. Long story short but they were using an application which you could only browse to folders, so using a shortcut was not an option so they used this feature to browse to the file server shared folders. The fix was kind of simple, on the file server just enable the "Function Discovery Resource Publication" service.

I recently had a request from a user where they wanted everyone in their department to have a particular folder location mapped in their Quick Access location. I came across a Powershell script which is able to do this $o = new-object -com shell.application $o.Namespace('Folder location here').Self.InvokeVerb("pintohome") I did then have further problems with SCCM not being able to deploy this script as it kept coming up with 0x01 error. To get around this I then had to create a package which was a batch file calling the powershell script with the following command: powershell.exe -executionpolicy remotesigned -File "File Location and name.ps1" exit /b %errorlevel% Note when doing this I had to run with the user's rights rather than the local administrators, and also set it to run only when a user is logged on.

I recently just upgraded our SCCM to 1710 and was eager to try out the new feature of setting up child task sequences. However for a while I was confused when I was going to test this out the option I had read about "Run Task Sequence" was missing. I stumbled upon this blog post on WindowsNoob and this explained the issue - https://www.windows-noob.com/forums/topic/15965-how-can-i-enable-the-run-task-sequence-step-in-sccm-current-branch-version-1710/ So in summary you need to go to Administration - Hierachy Settings and enable "Consent to use pre release functions" You then need to enable the Run Task Sequence Restart your console and the changes will apply