Hi folks,
I am a member of the team that releases Microsoft Exchange updates out to the general public (my previous introduction), and I wanted to explain a bit about WSUS (Microsoft Windows Server Update Services) and how we treat cluster vs. non-cluster installs.
I understand that lack of ability to ‘deadline’ packages can cause WSUS administrators grief, especially when they have many computers to update. Previously, Exchange updates could not offer the ‘deadline’ ability because WSUS turns it off globally if it detects that any package in the bundle requires a manual install. So Exchange updates would contain both the cluster and non-cluster packages. Yes, I had to place the same package twice in an update to handle the two different scenarios. Given that I wanted to enable WSUS administrators to have automated installations for non-clusters, I decided to tackle the problem by breaking up these two scenarios and begin releasing two separate updates for Exchange 2003 updates. I have not done this for Exchange 2000, as we would have had to re-release the Exchange 2000 post-SP3 Rollup. Moving forward, for every Exchange 2003 update that is pushed out, WSUS admins will see two versions of the update. We will still target each update to a specific release/service pack of Exchange. The non-cluster version will be labeled “Non cluster” and ‘deadline’ will be possible. The cluster version will be labeled “Cluster” and will still not have the ability of ‘deadline’ because of the manual installation requirement.
So here it is:
Exchange 2000 Server Service Pack 3 (KBXXXXXX) Will target both cluster and non-cluster Exchange Server 2003 Service Pack 1 (KBXXXXXX) - Cluster Will target cluster installations Exchange Server 2003 Service Pack 1 (KBXXXXXX) – Non Cluster Will target non-cluster installations Exchange Server 2003 Service Pack 2 (KBXXXXXX) - Cluster Will target cluster installations Exchange Server 2003 Service Pack 2 (KBXXXXXX) – Non Cluster Will target non-cluster installations
Exchange 2000 Server Service Pack 3 (KBXXXXXX)
Will target both cluster and non-cluster
Exchange Server 2003 Service Pack 1 (KBXXXXXX) - Cluster
Will target cluster installations
Exchange Server 2003 Service Pack 1 (KBXXXXXX) – Non Cluster
Will target non-cluster installations
Exchange Server 2003 Service Pack 2 (KBXXXXXX) - Cluster
Exchange Server 2003 Service Pack 2 (KBXXXXXX) – Non Cluster
Note: IMF updates are not addressed with this blog.
Scott Roberts
How about creating new classifications for Cluster and Non-Cluster as organisations will generally have one type of exchange set up or the other. Having seperate classifications can then me we can ignore the one we don't want / don't approve the wrong updates as they can be filtered.
Very interesting writeup thank you.
Understands that lack of ability to ‘deadlines’ package can cause WSUS administrator grief wonderful
Previous, Exchange update could not offer the ‘deadline’ abilit's because WSUS turn it very good
WSUS administrator to have automated installation for non-cluster thanks
So Exchanges update would contains boths the cluster and non-cluster package very nice
By breaking up these two scenario and begins releasings two separates updates for Exchange 2003 update very good
http://www.batteryfast.co.uk/asus/a32-u5.php Laptop Battery fit ASUS U5A U5F 90-NE62B2000 A32-U5 NEW laptop battery,
http://www.batteryfast.co.uk/compaq/191169-001.php New battery fit Compaq NC6000 NW8000 V1000 NC8000 NX5000 laptop battery,
http://www.battery-export.com/dell/dell-latitude-c600.html Dell Latitude C600
http://www.battery-export.com/dell/dell-latitude-c610.html Dell Latitude C610
http://www.battery-export.com/dell/dell-latitude-c640.html Dell Latitude C640
Thanks so much for this! This is exactly what I was looking for
www.mircse.com http://mircse.com Sohbet Portali
thank's and happy
http://www.ircask.com
yahoo google