Thursday, January 20, 2005
Virtual PC 2004 SP1.27 Upgrade Experiences
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
Multiple Versions of Virtual PC 2004 SP1!
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
Exchange Best Practice Analyzer Tool update
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
Junk e-mail Filter updates on Outlook, Entourage (and IMF?)
Thursday, January 06, 2005
Kit - Upgrading to Exchange 2003 in a Medium-Sized Organization
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
Beat Hackers At Their Own Game With A Hackerbasher Site
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.
MOM 2005 Performance and Sizing White Paper
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... ;)
Friday, December 17, 2004
Nice Little Tool To Kill Applied Group Policies
Thursday, December 16, 2004
CPU / Memory Scalability of Exchange 2000/3
The maximum amount of memory that Exchange can make use of is 4 GB (old news) but more interestingly is that the article recommends disabling the use of PAE (Physical Address Extension) on Enterprise and Datacenter versions of Windows with the use of the /nopae boot.ini switch (If using the /3GB switch) - as it puts unnecessary strains on the system.
New facts to me are the notes regarding the scalability of Exchange in terms of CPU's - on a 8 CPU system Exchange supposedly can fully utilize 900 MHz CPU's but it isn't able to utilize e.g. 8 1400 MHz Xeon CPU's (Unless you are running e.g. anti-virus products on the same boxes).
Phishing - Paypal example
Phishing
Get in the Christmas mood ;-)
Wednesday, December 15, 2004
WINS Security Issue #3
Unfortunately, the original KB article does not say anything about the patch.
Exchange 2003 Operations Checklists
I would classify the content in these checklists as very good things-to-remember lists - as they by no means are complete. But they are indeed a good start when preparing the disaster recovery procedures and operational processes for an Exchange 2000/2003 deployment (and of course many of the checks on the lists could be implemented in e.g. MOM 2005 instead of doing it manually).
Protecting your administrative permissions #2
Sunday, December 12, 2004
WINS Security Issue #2
If you do not have an existing IPSec policy, I recommend that you deploy this method right away. The easist deployment may be to do it with psexec or modify the script as ipseccmd.exe can take a server name as the first argument.
Friday, December 10, 2004
Using a Dedicated AD Site for Exchange
Microsoft just released a new paper on this. When running Microsoft® Exchange Server 2003 or Exchange 2000 Server in larger environments, the frequency of queries to the Active Directory® directory service can be very high. Exchange Server uses its directory access component to communicate with Active Directory domain controllers and global catalog servers to perform tasks such as e-mail address lookups, distribution group expansion, Microsoft Outlook® client proxy, and referral services. With such a heavy load being placed on domain controllers, Microsoft IT optimized the performance of Exchange when communicating with Active Directory by creating a new Active Directory site and isolating domain controllers and global catalog servers just for Exchange. Get it here.
Thursday, December 09, 2004
Protecting your administrative permissions
Microsoft has an article called Browsing the Web and Reading E-mail Safely as an Administrator - which actually refers to Aaron's blog :). The article has a DropMyRights utility, which is able to remove your permissions while starting an application. This is also a useful approach - e.g. run Internet Explorer and Outlook with lower permissions.
Finally, there is work-around of how to start Windows Explorer as another user from runas - Aaron again. I used to start iexplore.exe to do this trick, but it seems that if only you start it with the /root argument, it will start in its own instance. Read about that here. You can also read about a useful toolbar, that shows the current credentials.
Tuesday, December 07, 2004
WINS Security Issue
Currently, there are no known incidents - and maybe WINS servers are too few worth attacking. If you do not implement one of the suggestions - after you have considered the situation carefully - at least follow the situation in the press and be ready to take action.