So my System Center (sic) alert logs are constantly being bombarded with
In PerfDataSource, could not find counter Process, Working Set, IEXPLORE* in Snapshot. Unable to submit Performance value. Module will not be unloaded..........
It appears it’s a well known fault with an equally well known workaround, a few clicks of the mouse and it’s all quiet on the SCE front!
Data Protection Manager (DPM) relies heavily on the Virtual Disk Service (vds.exe).
As your backup sizes grow and uptime increases it’s not unusal for VDS to consume all free memory, adding more RAM to the DPM server just delays the inevitable.
With a bit of hunting I found the following symptoms and related hotfix 958387.
A memory leak occurs in the Virtual Disk Service when an application uses the Virtual Disk Service to enumerate disk resources. In this scenario, you notice that the memory consumption of the Virtual Disk Service (Vds.exe) increases continually.
So far so good… here’s hoping the issue is long gone
So i got sick of hearing the system beep chiming through the office, luckily there’s a service that can be stopped to bring silence back.
net stop beep
will do the trick for a temporary fix, to stop it permanently just disable the service
sc config beep start= disabled
The process of configuring a SSL certificate has changed between IIS6 and IIS7.
Here is how to create a new AD Domain based SSL certificate and apply it to your virtual site.
Creating the Certificate
Open IIS Manager and select the instance.
Select Server Certificates
I’ve been going through a few headaches with deploying System Centre alongside ISA 2004.
All of my managed servers/computers were coming up with the following status
MODEL: unkown
Last Contacted: not contacted
Deployments and Inventory: error
After a bit of poking around I worked out it’s related to the windows update service.
One one of the workstations I inspected the WindowsUpdate.log file and came across this entry
Server URL = https://systemcentre.foo.local:8531/SimpleAuthWebService/SimpleAuth.asmx
WARNING: GetAuthorizationCookie failure, error = 0×80244021, soap client error = 10, soap error code = 0, HTTP status code = 502
Browsing from the workstation to https://systemcentre.foo.local:8531/SimpleAuthWebService/SimpleAuth.asmx gave me the error
Error Code: 502 Proxy Error. The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests. (12204)
To get around this, I installed ISA Tunnel Port Editor and added port 8531 to the SSL tunnel range.
I recently used GParted to resize a server 2008 partition, all went swimmingly until I rebooted and was prompted with a Windows Boot Manager error.
File: \Windows\system32\winload.exe
Status: 0xc0000225
Info: The selected entry could not be loaded because the application is missing or corrupt.
The Fix
1. Boot the windows server 2008 cd
2. Select your language
3. Select repair your computer
4. c:\
cd \windows\system32
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
5. Restart
I have since learned that you can just use shrink volume from within the storage manager.
If you’re planning on running 2003 and 2008 domain controlers in the same domain you need to update the AD schema on all of your 2003 DC.
To do this pop/map the CD and execute the following
d:\sources\adprep\adprep.exe /forestprep
d:\sources\adprep\adprep.exe /domainprep /gpprep
d:\sources\adprep\adprep.exe /domainprep /rodcPREP
The lack of a GUI tends to make simple tasks that little bit harder, ie installing VMware tools.
Start the install as per normal by clicking on Install/Upgrade VMware Tools. You’ll find that nothing will happen, well not quite you now have a cdrom (d:\).
In the command prompt execute the following, obviously replacing d:\ with what ever drive letter was mapped.
msiexec.exe /i “d:\VMware Tools.msi” /qn
Once installed the server will reboot.
http://technet.microsoft.com/en-au/bb978329.aspx
WSS maintains time zone information independently of the host operating system in the text file TIMEZONE.XML. Traditionally, hotfixes were used to update TIMEZONE.XML, but in November 2007 it was decided that this was not the most efficient way to make these changes, and development of an alternative mechanism was started. Until this work is completed (the estimate is early in 2008), TIMEZONE.XML will need to be updated manually.
To prepare WSS for a daylight saving change, the following steps need to be performed:
I needed an easy way of working out how many active users are on the network in a 60 day period.
I realise I could have done this with DSQUERY/DSGET but I figured it’s high time to learn powershell.. So, this is my first real foray into Windows PowerShell.
To make my life easier I Installed PowerGUI and enabled the Active Directory QAD cmdlets.
The script below searches for all accounts that were logged in within the last 60 days, it only searches in the users OU as specified by the $searchRoot variable.