The WS-Management service cannot process the request

The WS-Management service cannot process the request. The user load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least X milliseconds.

I had this issue just a couple of times in Exchange 2010, but when it happens it’s a pain as you can’t run a single powershell command against exchange. Most of the resolutions I found online talked about increasing some policies or making changes in AD.

None of this is required (or at least I wouldn’t start making any change until I tried all of the soft-changes), what helped me fix the “The WS-Management service cannot process the request” problem was to restart IIS. You can do that by running a command prompt with elevated rights and type:

Note: if you have a monitoring system or load balancers that notify your entire team when HTTP/HTTPS go down, IISRESET will send in an alert.

Read More

DPM 2010 Console won’t start (ID 948)

Unable to connect to Servername (ID: 948). I spent a good hour trying to understand what happened here. DPM used to work just fine on this server up until a controlled reboot was performed. I came across a few solutions on the internet and only one of them worked for me. It wasn’t even easy to spot! I’ll be reporting the other solution as well as I think it might fix it for other people.

So here’s the error when you try to launch the DPM 2010 Console:


When I went and checked the services, all of the DPM ones were in a Stopped state (even though the server tried starting MSDPM every few minutes). When I tried to manually start them, I got the following error:


Note that I tried to restart the SQL Server service as well and then tried again to start DPM, with no luck. This is how an healthy server should look like in terms of DPM services:


And SQL Services:


Let’s see the two solutions for this issue [DPM 2010 Console won’t start (ID 948)].

Solution 1

After looking and looking I came across a solution that unfortunately didn’t work for me, but I want to mention it as it did fix issues for a few users. (more…)

Read More

SCCM USB Stick not booting

If you’re having issues with an SCCM USB stick not booting, that perhaps used to, then it most likely needs some manual input to help it go through.

When you build a USB stick in SCCM, you have the option to Format the USB stick and make it bootable but even after that, it still doesn’t work. Note that the BIOS does recognise it as a bootable media and shows in the bootable devices so that makes you think even more that there’s a different problem.

The solution for the SCCM USB Stick not booting is pretty simple, follow this step and you should be good (these had to be followed already prior SCCM 2012).

  1. Connect the USB stick to a Windows Vista+ device.
  2. Run a command prompt as administrator.
  3. Type DISKPART and press enter.
    1. The command prompt will now take a few instants to go start diskpart
  4. Type LIST DISK and press enter.
    1. This will return the list of disks attached to the machine. Note the Disk Number. In this example we’ll assume the USB disk is DISK 1.
  5. Type SELECT DISK 1 and press enter.
  6. Type CLEAN and press enter.
    1. This command will wipe everything off the USB stick. Make sure you selected the right disk 🙂 .
  7. Type CREATE PARTITION PRIMARY and press enter.
    1. If you receive an error here, then you most likely need to grab a new USB stick.
  8. Type SELECT PARTITION 1 and press enter.
  9. Type FORMAT FS=FAT32 QUICK and press enter.
  10. Type  ACTIVE and press enter.
  11. Type ASSIGN and press enter.
    1. This will assign an available letter to the drive.
  12. Type EXIT and press enter to leave diskpart and repeat this step to exit the command prompt.


Read More