Category Archives: IT Tips

Install / deploy Office Professional Plus 2019

Microsoft released Office 2019 yesterday. But it seems Microsoft push very hard to get people move from traditional office to office 365.

After I login Microsoft Volume Licensing Service Center, I found that Microsoft stopped to provide the ISO for Office Professional Plus 2019. And Microsoft only provides the deployment tool to deploy office 2019.

Office Professional Plus 2019 will be released with Click-to-Run installation technology only. We are not providing MSI as a deployment methodology for Office Professional Plus 2019.

Ok, then how can we install Office Professional Plus 2019?

First of all, download Office_Deployment_Tools_2019_MLF_X21-88134.exe from Microsoft website.

Then create an xml file as following:

Please be aware “ProPlus2019Volume” is the only available channel for office 2019 “ProPlus2019Volume”.

3. Run below command to get office 2019 installed

And you can also download a copy of the installation files if you want via below command:

Prevent Windows 10 from Locking When Monitor Turns Off

1,open the registry.

2. Browse the following path:

HKEYLOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\8EC4B3A5-6868-48c2-BE75-4F3044BE88A7

3. On the right side, double-click the Attributes DWORD.
Change the value from 1 to 2.
Click OK.

4.open the Power User menu and select Power Options.

5.Click the Change plan settings link for the selected plan. then click the Change advanced power settings link.

6 .On Advanced settings, scroll down and expand the Display settings.
You should now see the Console lock display off timeout option, change the default time of 1 minute to the time you want, in minutes.
Click Apply.

Click OK to complete the task.

Reading a memory.dmp or other .dmp file

This can be accomplished with 7 easy steps:

Step 1. Obtain and install the debugging tools.

Debugging Tools Windows

All you need to install is the “Install Debugging Tools for Windows as a Standalone Component (from Windows SDK)” and during the install only select “Debugging Tools for Windows”. Everything else is used for more advanced troubleshooting or development, and isn’t needed here. Today I followed the link to “Install Debugging Tools for Windows as a Standalone Component (from Windows SDK)” although for a different OS you may need to follow a different link.

Step 2. From an elevated command prompt navigate to the debugging folder. For me with the latest tools on Windows Server 2012 it was at C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\. You can specify the path during the install.

Step 3. Type the following:

kd –z C:\Windows\memory.dmp (or the path to your .dmp file)

Step 4. Type the following:

.logopen c:\debuglog.txt

Step 5. Type the following:

.sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols

If you computer can’t connect to internet, you can download the symbols from below link:

https://developer.microsoft.com/en-us/windows/hardware/download-symbols

Step 6. Type the following:

.reload;!analyze -v;r;kv;lmnt;.logclose;q

Step 7. Review the results by opening c:\debuglog.txt in your favorite text editor. Searching for PROCESS_NAME: will show which process had the fault. You can use the process name and other information from the dump to find clues and find answers in a web search. Usually the fault is with a hardware drivers of some sort, but there are many things that can cause crashes so the actual analyzing of the dump may take some research.

Often times a driver update will fix the issue. If the summary information doesn’t offer enough information then you’ll need to dig further into the debugging tools or open a CSS case with Microsoft. The steps above will provide you with a summary mostly-human-readable report from the dump. There is much more information available in the memory dump although it gets exponentially more difficult to track down the details the further you get into windows debugging.

Hopefully these quick steps are helpful for you as you troubleshoot the unwelcome BSOD.