Comments
-
Yes, I was just sharing my experience with the switches you asked about. Sorry if I buggered things up. Thanks, David
-
Here is a script monitor I use to monitor our mailbox stores: In the command line you specify 4 parameters. The system mailbox is unique to each mailbox store so that's how it determines the correct mailbox store. David
-
Worked for me too Josh. You 'Da Man! Dave
-
It appears to be a valid command for 2008. Give it a try. Dave
-
I don't use patch manager so I'm sorry. Dave
-
That's a great way to do it Pedro and that is what I do as well for Workstations and servers. I just updated a few hundred servers and I swear to get the server to synch up with WSUS after a patch application and reboot was to run detectnow, then reportnow, then detectnow. It's the only thing that would work. Dave
-
I just installed APM 2.5 and so far it looks like there have been some nice features added. I'll know in a few days if it resolved the Event ID 333. Thanks, David
-
KUDOS! Web.config mod fixed me too. Thanks, Dave
-
@bellch. If you can confirm the system mailbox does indeed exist you might want to reboot the server. This was the fix for that in all the cases I observed that issue. David
-
@grahampriley - I have not tried it with anything other than 2003. If there is a SystemMailbox in a mailbox store this script can monitor it's status and thus determine if the store is available. If there is not a systemmailbox you could create a special account with a mailbox and specify that as the for the command line…
-
Sorry for the late reply. Nothing in the script needs to be changed to suit your environment as that is all determined by the command line arguments. Set up a script monitor in APM and select this template as the code. David
-
Actually I meant to say "individual mailbox stores" Thanks.
-
Execute wuauclt /reportnow to update WSUS with the computers status then run wuauclt /detectnow to check for available updates. Dave