Tuesday, June 27, 2017

Migrate Windows Deployment Services to New Server

We have been making a great effort to move all of our internal services to Windows Server 2016. This past week, it was WDS' turn to get migrated. Migrating this role is extremely simple. Here are the steps that I took:

  1. Create new server and install WDS role.

  2. Stop WDS Service on old server

  3. Stop WDS Service on new server

  4. Use my "Copy-Files" PowerShell script (Available Here: Copy-Files.ps1) to copy RemoteInstall Share to new server

  5. Start WDS Service on new Server

  6. Shutdown old WDS Server completely

  7. Update option 66/67 in DHCP scopes to reflect new WDS Server

  8. Update any appropriate DNS records


Note:

If you are unable to start the WDS service, delete the WDS database and logs from the old server located at <drive letter>:\RemoteInstall\Stores\Metadata\*.*. You should be able to start the service after deleting these files.

Simple enough! :)

Monday, June 26, 2017

New Script: BulkAdd-SpamFilterWhitelist.ps1

This script is capable of adding a list of domains to an Exchange Online Spam Filter policy. It can be downloaded from TechNet or Github.

Github

TechNet

Unable to Power on Virtual Machine - A General System Error Occurred: Connection Refused

Hi there,

Earlier today I cloned a VM in one of our vCenter appliances. The cloning process completed without a hitch (as it usually does). However, I was not able to power on the VM. I looked at the "Tasks" view in vCenter and found this:



This is a fairly generic error message. However, the "Connection Refused" part prompted me to take a look at the vCenter services. You can view these services by browsing to Home > Administration > System Configuration > Services in the vSphere Web Client for vCenter. On the Summary tab, there is a handy "Services Health" section that will give you a high level overview of the overall health of the services. You can see here that three of the services are in a critical state on my vCenter appliance.



You can hover your mouse pointer over the critical services link and view the critical services. You can also click on each service to get a better view of the status. The Postgres database service on my appliance was one of the services in critical state. I clicked on it and viewed the screen below. You can see here that the problem is obvious, the filesystem holding the Postgres database service is completely out of space. I was able to identify that the log directory was the culprit.



Its simple enough to SSH into the appliance and delete the logs. However, this will not prevent the problem from happening again. After doing some Googling (I love that the Merriam-Webster dictionary identifies this as a real word in the English language!), I found these KB articles:

Follow this one to decrease the maximum backup size and maximum backup index size of the SSO logs in the log4j.properties configuration file:

/storage/log directory is full in vCenter Server Appliance 6.0 (2143565)


To offload your logs to a syslog server, follow this article:

Redirect vCenter Server Appliance Log Files to Another Machine

This will prevent the log directory from consuming the entire partition again. After following these steps I rebooted the vCSA for good measure and was able to power on the virtual machine after doing so.

Hopefully this will help someone who is having the same (or similar) problem!