Tuesday, December 25, 2018

Forcefully Clear the Print Queue in Windows Servers

Go to Start, Control Panel and Administrative Tools. Double click on Services icon.



Scroll down to the Print Spooler service and right click on it and select Stop. In order to do this, you need to be logged in as Administrator. 
(NOTE: No one is able to print once the service is stopped)

Browse to C:\Windows\System32\spool\PRINTERS
There are two corresponding files for each print job, a .SPL file and a .SHD file. Delete both files

start the print spooler back up by right-clicking on it and selecting “Start.

Refresh the window on the print queue and it should now be gone!


Friday, November 2, 2018

Where is Microsoft Outlook 2016 for Mac Database?

Outlook 2016 for Mac stores its database in:

Users/*Name*/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/

When the application does a database rebuild it is going to create a backup copy and place it into the above folder. Therefore please ensure there is sufficient storage space before you start to rebuild the database.


Tuesday, October 16, 2018

Jamf agent installer failing to install / re-install

At some point when the machines happen to be out of the office network for a period of time, you might notice Jamf agent fail to sync with your server. When you attempt to perform a reinstall to let it resync an error message appear.



You need to perform below step on the affected Mac machines and it should resolve the issue.

Go to spotlight type "/usr" enter


Go > local > jamf (delete the jamf folder)


Empty the trash bin and re-run the installation package.

If you still encounter the error message, try to re-create Jamf package.

Tuesday, September 25, 2018

HP Laptop G3 imaging with MDT - blue screen

Purchased new HP 820 G3 and Dell 7270 after completed imaging using MDT the laptop will be restarted and a blue screen will display.















At first, though there some issue with the hardware, after performing diagnostic no fault found. The second thought which came to my mind is the drivers because our environment is mixed with Dell and HP brand and I believe the problem was the conflict of drivers between the two brand also could be due to older drivers not remove (I never perform drivers clean up since day 1, which is not recommended).

I went through the list of drivers for both brand and perform clean up but fruitless result. And doing some research and getting advice from colleagues from other market and the issue might be the startup setting.

After changing the start-up setting. from legacy to UEFI, the laptops working as per normal.

Thanks to this incident, I got a chance to perform drivers cleaner for the MDT.