Thursday, January 27, 2005
An alternative is to do it from the command line using WMIC. Take this statement - it was part of an SMS error message I got:
SELECT __CLASS, __PATH, __RELPATH, Description, Manufacturer, Name, Status FROM Win32_NetworkClient
You can not use the statement directly, but it can easily be converted to WMIC style:
wmic path Win32_NetworkClient get __CLASS, __PATH, __RELPATH, Description, Manufacturer, Name, Status
Use the /Format switch to make the output more readable.
*) In case you do not know wbemtest, play around with it. Just search the Help and Support Center for wbemtest.
Tuesday, January 25, 2005
If you by chance should experience the same situation on NT4, the error is also a strange one. As I'm not 100% sure, I'm not going to provide the message but it had something to do with file/record already exists.
Sunday, January 23, 2005
The next version of Hosted Exchange 2003 (HE2003), Krakatoa, now renamed to Hosted Messaging and Collaboration 3.0 (HMC 3.0) has been released. It continues the evolution from HE2003 and adds "true" support for Sharepoint Services and Live Communications Server 2005. Furthermore the reference architecture has been updated significantly with -
Support for running on MPS on Windows Server 2003 (As opposed to HE2003)
SQL Reporting Services
Microsoft Operations Manager 2005
Migration tools from to migrate users from other platforms
Intelligent Message Filtering
Resource Manager Rebuilder Tool (Used when AD and MPS is out of sync)
OAB Migration Tool (Used when moving from "standard" Exchange OAB implementation to dedicated OAB servers)
And much more - I will be back with further info when I've had the time to test and use the product. Until then you can check links to the press release here and what the press has to say about it here.
Thursday, January 20, 2005
So I tried to update. But the SP1.27 (as I now call it) said the software already was installed. I went into Add/Remove Programs and uninstalled SP1. Planning on rebooting later, I found that the uninstall made all my network adapters unusuable. Normally, the install disables networking temporary, but this time they simply did not work afterwards.
After rebooting, I realized that Virtual PC was completely uninstalled. I installed the RTM version again and applied SP1.27.
Now both Help, About and Add/Remove Programs, Support Information claims that I'm running 5.3.582.27 as expected.
Wednesday, January 19, 2005
Now to the strange part. The download was SP1 - but I already upgraded to SP1 last year?? I took it one step deeper and came up with these version numbers:
- RTM report (build 582) - ORCA say 5.3.582
- My running SP1 is 5.3.582.23 - but Add/Remove Programs 'Click here for support information' says 5.3.582.24?
- I already had a saved, downloaded SP1 kit - it is 5.3.582.24. Obviously, I did not use this when I upgrade - or did I?
- The new download is 5.3.582.27
SP1 is not SP1 - I think I will upgrade again...
Tuesday, January 18, 2005
Missing Exchange binary files, presence of recovery storage groups, availability check for the primary DNS server, Exchange process TCP port conflicts, and checks for over 25 non-default settings.
Find it here
Thursday, January 13, 2005
Thursday, January 06, 2005
The kit contains three documents (and a small checklist); the first of these takes the reader through the high level deployment steps and a decision flowchart to check whether or not the readers organization is a candidate for the "standard deployment method" - the second document contains instructions for an in-place domain upgrade and the last document contains instructions for upgrading the Exchange environment.
IMHO one of the best features of this deployment kit is that it has an reasonable size (less than 80 pages) and that it gives the reader a very good overview of the steps in a standard Exchange/domain upgrade - whether or not the "standard deployment method" is a viable method for all readers is another case; but more important is that it gives the reader a good background for e.g. a discussion with their professional advisors regarding deployment methods.
Sunday, January 02, 2005
In this article, I will present an easily implemented strategy that uses HTTP 1.1 host headers to divert port 80 attacks away from unsecured public Web sites into a dead end where they can't do damage.
Make sure to read the Hardening Your Web Server sidebar for further ideas.
Next, Microsoft ended 2004 by finally releasing a white paper on MOM sizing. It is going to be fun to see whether the systems I have implemented meets the requirements... ;)