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
Monday, June 26, 2017
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:
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!
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!
Thursday, June 22, 2017
Windows 8 File History
File History
File history in Windows 8 allows users to automatically “backup” files that are in their libraries, contacts, favorites, Skydrive, and on the desktop. If the files are lost, they can be quickly restored. You can also restore a file from a specific point in time, being that File History creates a complete history of your files over time. You will need a separate drive other than the one you have Windows 8 installed on to use File History. To begin using it, connect an external drive and search for File History on the Start Screen:
After opening File History, you will see this screen:
To enable File History, click the ‘Turn On’ button. You can select the drive you want to use by clicking ‘Select Drive’ on the left hand side from this same screen. The first time you enable File History, it will create a full backup of all files on your computer, except for files that you do not access (system files), and files you have chosen to exclude. From then on, it will create a versioned copy of every file that has changed since the last backup.
You can use a locally attached drive or a network share for File History. To choose how often File History backs up files; choose ‘Advanced Settings’. From here you can also choose how much space on the drive is used, and how long saved versions of files should be kept.
When the total space allocated to File History has been used, the feature will delete the oldest versions of files to make room for newer versions.
Subscribe to:
Posts (Atom)