Sunday, October 28, 2018

How to Install VMware ESXi 6.7 on VMware Workstation 15

Static IP configuration were causing me some headaches. The alternative options are DHCP and DHCP with a reservation if you have a DHCP server you manage. Optionally, you can go the static configuration route but it was a headache for me and I'm busy and have other things to do.

Lab Scenario with VMware Workstation 15 (WS15 was on W10)

1. Download the ISO and then double-click until you find the .ova and double-click it or right click and open it in VMware Workstation. The wizard is pretty simple.

2. After you import the VM and configure the VM with the Wizard. VMware Photon 1.0 will launch and run the scripts in the background. Be patient. It runs for like 5-8 minutes. Just leave it alone. It will boot and you will see the screen. NOTE: Make sure you type in :5480 after the IP or the hostname or you will see bupkis.

https://ipaddress or FQDN:5480. I recommend using the FQDN

3. Select the option that works for you and install everything.


Wednesday, October 24, 2018

How to Create a Bootable .wim File

1. Download Rufus (Windows Based Systems) / Linux WinUSB doesn't work worth a damn on Ubuntu 18.04.1 LTS at the time of this writing so don't waist your time. (Don't download it anywhere else)

2. Grab your W10 EE/Pro ISO Image if you don't have VLSC: (You need a license if you need it more than 90 Days, but for testing/evaluation/school purposes, it's fine.)

3. Launch Rufus and configure the ISO

4. After everything is done. Open the USB and delete the "install" .wim file from \sources and replace it with your .wim file and then rename it  to "install"

5. Boot that sucker and verify everything is working. You're done.


Tuesday, October 9, 2018

How to Create Bootable Windows 10 USB on Ubuntu 18.04.1 LTS

1. Open Disks app on Ubuntu and format the drive NTFS

Do It The Hard OCD Way:

2. Grab the source code from WoeUSB:

3. Open Terminal and create a location for WoeUSB:

4. sudo mkdir /opt/woeusb

5. cd /opt/woeusb  && git clone

6. In order to run mk-build-debs you need to install devscripts

7. sudo apt-get install devscripts equivs gdebi-core -y (NOTE: Remove when your done for security of your system)

8. Then prep the environment: sudo ./setup-development-environment.bash

9. cd /opt/woeusb/WoeUSB/ and then run sudo mk-build-deps

10. sudo gdebi woeusb-build-deps_*

Do It the Fast...I Don't Have Time, I'm Busy Way:

2. sudo add-apt-repository ppa:nilarimogard/webupd8 && sudo apt-get update -y && sudo apt-get install woeusb -y


Tuesday, October 2, 2018

How to Fix "The Specified Virtual Disk Needs Repair" on VMware Workstation 15 on Ubuntu 18.04.1 LTS

You try to enlarge the disk and you run into the error about the disk needing repair.

Verified that works on VMware Workstation 15 on Ubuntu 18.04.1

1. Open terminal on the machine you have VMware Workstation installed

2. /usr/bin/vmware-diskmanager -R /path/to/.vmdk file

3. Go to settings of the VM and try your advanced operation to compact the disk or expand it. Bam...done.


Wednesday, September 26, 2018

How to Remove Windows 10 Bloatware Permanently

First and foremost...I want to thank at least 10 different bloggers for posting general information and one of the most helpful was Daniel's IT Blog. and Andre Picker (This is for removal of the unwanted W10 Apps from .WIM only)

This is for an IT Image for Windows 10. Why on earth Microsoft doesn't have an "IT" script to remove all the junk they know damn well will never go on a business, enterprise or government computer is beyond me. So we IT Managers, Solution Architects, Systems Engineer's are left figuring out ways to remove the crapware so user's don't put in a million tickets asking questions about using the software or locking their machine up doing something crazy no one anticipated.

Here you go:

1. You can use a Powershell script from How-To-Geek: but for IT purposes. It's only removing the junk from one profile. Not the entire machine. As soon as you log in with another user.'s back like a software cancer.

2. You have to disable things in the registry for it to be permanent or you can rely on some task to run from SCCM, but they're not always reliable and many times it appears and then the script has to run for it to disappear. Again, this will do nothing but generate support tickets and unnecessary calls about "What is this thing on my machine? Do I have a virus?".

3. #1 Rule of IT and Troubleshooting. Never give up. Somebody has solved the problem or you will get close enough to fix the issue yourself.

4. Completed on Windows 10 Enterprise Version 1803. OS Build 17134.285

5.  Launch services.msc and stop and then disable the services you don't need (this worked for me, but you may do something different):

Touch and Keyboard and Handwriting
Hyper-V (All)
Microsoft iSCSI
Microsoft App-V Client
dmwappushsvc (Data Collection service)
Downloaded Maps Manager (Microsoft Maps)
Phone Service
Remote Registry
Retail Demo Service
Routing and Remote Access (Unless you have a business need)
User Experience Virtualization Service
Windows Backup
Xbox Settings (All) - FYI. You have to disable the Xbox Gaming Monitoring Feature in the Registry. It won't disable from services.msc. Great Tutorial to Disable in the Registry:

6. Disable the crapware/bloatware permanently (Thanks Daniel:

Disable by changing to a [0]

7. Create a new local account and verify everything is disabled.

Start >> Settings >> Family & other people >> Add someone Else to this PC >> Click on "I don't have this person's sign-in information >> Click Add a user without a Microsoft Account. >> Type in your username, password and temporary recovery. You will be blowing this away. It's just for testing so don't bother getting all fancy.

8. Those of us that have been around for a while know about Computer Management. Just use this one and blow it away when your done. 

9. If you have to find the account you created (like you joined it to the domain BEFORE you removed it and started working on it locally in a VM...cough...cough). You can find the buried System Properties under Control Panel:

10. Go under Settings and delete the other profiles (Domain Accounts you cannot delete from Computer Management. (*While you're at it, Adjust for Best Performance). PRO TIP: Just leave the thing open. You will be blowing away test accounts.

11. OCD Style (Be Careful):

Delete the packages under C:\MSOCache\All Users\ (One Note/Groove). If you have MS Office installed. Do NOT just go in there and wipe out all of the folders. 

12. PRO TIP: Turn the Hidden Files feature back off before you forget and do something terrible.

13. Windows System Apps Location: C:\WindowsSystemApps. This is where the files and executables are stored. 

14. Location of the files in the registry (FYI. Microsoft makes it difficult to edit these entries): 

15. Disabling the "PackageRoot" and "PackageRepositoryRoot" could cause unintended consequences. Test and configure to your liking.

16. Appx >> Config >> Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy >> SetupPhase [Default is 27] Changed to 0 (launches the new profile quicker)

17. Appx >> Config >> Microsoft.BioEnrollment_cw5n1h2txyewy >> SetupPhase [Default is 81] Changed to 0 (launches the new profile quicker)

18. At this point, the bloatware is still coming up on launch. Now we kill it. (FYI. I didn't mess with Windows Store at all since it can break all manner of things on updates, etc)

19. Before you run any PowerShell Scripts. You have to enable the ability to run Scripts on Windows 10. Right-click on PowerShell and "Run As Administrator"

PS C:\Windows\system32> Get-ExecutionPolicy
PS C:\Windows\system32> Set-ExecutionPolicy unrestricted

Click Y or S (Suspend) and then run your script

cd ~ to return to your profile location and then cd into your location of the PowerShell Script

20. Powershell easy peasy...Save it as "CleanUp.ps1" and cd to the folder from PowerShell and run it.

#Retrieved on 9.26.2018 from
#Be careful removing Windows Store from Windows 10 since it can
#have unintended consequences for Windows Updates
Get-AppxPackage *3dbuilder* | Remove-AppxPackage
Get-AppxPackage *windowsalarms* | Remove-AppxPackage
Get-AppxPackage *windowscommunicationsapps* | Remove-AppxPackage
Get-AppxPackage *officehub* | Remove-AppxPackage
Get-AppxPackage *skypeapp* | Remove-AppxPackage
Get-AppxPackage *getstarted* | Remove-AppxPackage
Get-AppxPackage *zunemusic* | Remove-AppxPackage
Get-AppxPackage *windowsmaps* | Remove-AppxPackage
Get-AppxPackage *solitairecollection* | Remove-AppxPackage
Get-AppxPackage *bingfinance* | Remove-AppxPackage
Get-AppxPackage *zunevideo* | Remove-AppxPackage
Get-AppxPackage *bingnews* | Remove-AppxPackage
Get-AppxPackage *onenote* | Remove-AppxPackage
Get-AppxPackage *people* | Remove-AppxPackage
Get-AppxPackage *windowsphone* | Remove-AppxPackage
Get-AppxPackage *photos* | Remove-AppxPackage
Get-AppxPackage *bingsports* | Remove-AppxPackage
#Do Not disable if you have any visually impaired
Get-AppxPackage *soundrecorder* | Remove-AppxPackage
Get-AppxPackage *bingweather* | Remove-AppxPackage
Get-AppxPackage *xboxapp* | Remove-AppxPackage

21. None SCCM Option/Failsafe Option:

Save the file under c:\Users\Default\AppData\Local\Microsoft\CleanUp\CleanUp.bat
The actual powershell file will live under c:\%WinDir%\system32\CleanUp.ps1

Batch File under AppData:
REM Run an unsigned PowerShell script and log the output
Powershell.exe -ExecutionPolicy Unrestricted .\%WINDIR%\system32\Cleanup.ps1 >> "%TEMP%\CleanUpLog.txt" 2>&1

REM If an error occured, return to errorlevel.
EXIT /B %errorlevel%

22. Setup a Task and configure it to run weekly or on login in or script in in SCCM

23. Remember when you are setting up a Task Scheduler item that you have to have a  bypass for the script to run. I don't recommend turning PowerShell scripting off because it can have a nasty impact on your environment is PS execution is off for all of your machines. Definitely, not a good idea.

Under Actions: Start a Program >> Program/Script: >> Type in powershell.exe >> Add Arguments (Optional): -ExecutionPolicy Bypass c:\path to your script

24. Test it under a demo user. (You will see now why I said just keep Computer Management Open.)

25. Before you shutdown the system and convert it to the .wim image. Make sure that you run disk cleanup and that you delete the unnecessary Windows Update files to shrink the image and cleanup the junk:

CMD Prompt:
C:\ net stop wuauserv
C:\ cd %windir%\SoftwareDistribution
C:\del /F /S /Q Download && Start .

Once in Downloads. Wipe it all out.

c:\net start wuauserv

26. Open Powershell as administrator and clear all of the system logs (so you know that everything is fresh):

wevtutil el | Foreach-Object {wevttil cl "$_"}

If you want to use Command Prompt instead:

for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1"

27. Type in cmd and then shutdown /s /t 00

28. Use this to remove the apps from the .wim (This is for removal of the unwanted W10 Apps from .WIM only) *FYI. Didn't work for me.


Tuesday, September 25, 2018

How to Disable SharePoint Features for Adobe Document Cloud Reader

1. Disable Adobe Cloud Features:

2. This is how you Disable SharePoint features:

2a. Right Click on FeatureLockDown and add a New Key and type cSharePoint

2b. Right-click on cSharepoint and add bDisableSharePointFeatures. Enter and type 1. 

3. You can also block all of the cloud services if you don't want your users doing anything from the cloud.

4. Now it's nice and clean! 

5. FYI. You can disable the "Sign In" button up top but it wipes out the tools. It's up to you.

6. Lastly, the more things that you disable. The more features will be locked down. If you disable bToggleAdobeDocumentServices your users will not be able to edit PDF files, create PDF's, Export PDF's, Combine files, etc.

How to Install VMware Workstation 15 on Ubuntu 18.04 LTS

1. Do a clean uninstall of any previous versions for a clean installation.

2. VMware Workstation 14 on Ubuntu 18.04 LTS

3. Open Terminal and run the following command:

sudo vmware-installer -u vmware-workstation

4. Download the file from VMware's website

5. from terminal cd to the location where you saved the downloaded file. Run the following command to make the package executable:

chmod a+x VMware-Workstation*

6. Execute the Installer from the command line:

sudo ./VMware-Workstation*

Create your location/path for the shared VM's. I made mine /opt/vmware/shared instead of the default