I just found this through a friend. This was one of the best tools in SMS 2003 for DP control.
It looks to be the same for SCCM.
http://www.myitforum.com/articles/42/view.asp?id=8904
By: Cory Becht
Posted On: 7/24/2008
This utility queries the primary site server for all of its distribution points including child sites and then displays the packages for each distribution point. You check or uncheck which ones you want on that distribution point. You can also copy the packages list from one DP to another.
This utility was done in Visual Studio 2005, so it does require .NET Framework 2.0
Version History:
1.3 - Now includes duplicating the packages of another distribution point.
1.2 - Updated to include new ConfigMgr 2007 classes for packages (SoftwareUpdate, BootImage, etc.)
1.1 - fixed multiple dp's per site error
1.01 - included "select all" button for packages.
Download the utility here:
12171Setup.zip
If you see this error in your CCM log when trying to install clients
CWmi::Connect(): ConnectServer(Namespace) failed. – 0x800706ba
It is because the SCCM Client uses Dynamic RPC connections for WMI communications and can cause problems when a firewall is in place between the clients and the servers. This scenario is not documented in the Client install firewall doc.
The document is talking about using the windows firewall on the client and not a WAN firewall located between the SCCM server and the SCCM Clients.
http://technet.microsoft.com/en-us/library/bb694088.aspx
The Document states:
Client Push Installation
In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:
-
File and Printer Sharing
-
Windows Management Instrumentation (WMI)
but it doesn’t say what ports are required for the WMI Communications.
Here is info I was provided:
***************************
ISSUE: Unable to deploy SCCM client to systems across firewall via client push
CAUSE: RPC Ports not open on firewalls
SOLUTION: You opened the port range above 1024 -5000 to allow for installation of the client.
***************************
This issue has been submitted to Microsoft with a request to have the documentation updated to include what ports are needed for WMI and RPC communications when using WAN Firewalls.
Just got this from a TAM:
*********************************
Microsoft will distribute Windows Internet Explorer 8 as a high-priority update through Automatic Updates for Windows XP Service Pack 2 (SP2) and higher, Windows XP Professional x64 Edition, Windows Server 2003 SP2 for x64 and x86, Windows Vista for x64 and x86, Windows Vista SP1 for x64 and x86, and Windows Server 2008 for x64 and x86.
The Blocker Toolkit which is available via the link below is intended for organizations that would like to block automatic delivery of Internet Explorer 8 to machines in environments where Automatic Updates is enabled.
http://www.microsoft.com/downloads/details.aspx?familyid=21687628-5806-4ba6-9e4e-8e224ec6dd8c&displaylang=en&tm
Additional information is provided below directly from the download page and is offered for your convenience and review. Full details and any updates and changes would be available via the site page directly.
*********************************
Full Details:
Toolkit to Disable Automatic Delivery of Internet Explorer 8
Brief Description
The Internet Explorer 8 Blocker Toolkit enables IT Administrators to disable automatic delivery of Internet Explorer 8 as a high-priority update via Automatic Updates and the Windows Update and Microsoft Update sites.
Quick Details
File Name:
IE8BlockerToolkit.EXE
Version:
1
Date Published:
1/5/2009
Language:
English
Download Size:
115 KB
Overview
To help our customers become more secure and up-to-date, Microsoft will distribute Windows Internet Explorer 8 as a high-priority update through Automatic Updates for Windows XP Service Pack 2 (SP2) and higher, Windows XP Professional x64 Edition, Windows Server 2003 SP2 for x64 and x86, Windows Vista for x64 and x86, Windows Vista SP1 for x64 and x86, and Windows Server 2008 for x64 and x86. This Blocker Toolkit is intended for organizations that would like to block automatic delivery of Internet Explorer 8 to machines in environments where Automatic Updates is enabled. The Blocker Toolkit will not expire.
Note:
- For computers running Windows XP or Windows Server 2003, the Blocker Toolkit prevents the machine from receiving Internet Explorer 8 as a high-priority update via Automatic Updates and the Express install option on the Windows Update and Microsoft Update sites; Internet Explorer 8 will be listed as an optional update with the Custom install option.
- For computers running Windows Vista or Windows Server 2008, the Blocker Toolkit prevents the machine from receiving Internet Explorer 8 as an important update via Automatic Updates on the Windows Update and Microsoft Update sites; Internet Explorer 8 will be listed as an optional update.
- The Blocker Toolkit will not prevent users from manually installing Internet Explorer 8 as a Recommended update from the Windows Update or Microsoft Update sites, from the Microsoft Download Center, or from external media.
- Organizations do not need to deploy the Blocker Toolkit in environments managed with an update management solution such as Windows Server Update Services or Systems Management Server 2003. Organizations can use those products to fully manage deployment of updates released through Windows Update and Microsoft Update, including Internet Explorer 8, within their environment.
- If you used the Blocker Toolkit to block Internet Explorer 7 from being installed as a high-priority update, you need to use the Internet Explorer 8 version of the Blocker Toolkit to block Internet Explorer 8 from being installed. There are different registry keys used to block or unblock automatic delivery of Internet Explorer 7 and Internet Explorer 8.
See the "Additional Information" section below for detailed instructions on configuring and deploying the Blocker Toolkit. The same information is also provided in the Help file included in the download.
Answers to Frequently Asked Questions can be found here.
System Requirements
- Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Server 2003 Service Pack 2 x64 Edition; Windows Server 2008; Windows Vista; Windows Vista 64-bit Editions Service Pack 1; Windows Vista Business 64-bit edition; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic 64-bit edition; Windows Vista Home Premium 64-bit edition; Windows Vista Service Pack 1; Windows Vista Ultimate 64-bit edition; Windows XP Professional x64 Edition ; Windows XP Service Pack 2; Windows XP Service Pack 3
You must have one of the supported operating systems installed to use this toolkit.
Instructions
Click on the link to download the package and select ‘Open’ to run the package. You will be asked to accept the end-user license agreement (EULA) before you gain access to the package components.
Additional Information
Toolkit Components:
The toolkit contains two components:
- An executable blocker script
- A Group Policy Administrative Template (.ADM file)
Blocker Script
The script creates a registry key and sets the associated value to block or unblock (depending on the command-line option used) automatic delivery of Internet Explorer 8 on either the local machine or a remote target machine.
Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Setup\8.0
Key value name: DoNotAllowIE80
- When the key value name is not defined, distribution is not blocked.
- When the key value name is set to 0, distribution is not blocked.
- When the key value name is set to 1, distribution is blocked.
The script has the following command-line syntax:
IE80Blocker.cmd [<machine name>] [/B] [/U] [/H]
Machine Name
The <machine name> parameter is optional. If not specified, the action is performed on the local machine. Otherwise, the remote machine is accessed via the remote registry capabilities of the REG command. If the remote registry can’t be accessed due to security permissions or the remote machine can’t be found, an error message is returned from the REG command.
Switches
Switches used by the script are mutually exclusive and only the first valid switch from a given command is acted on. The Script can be run multiple times on the same machine without problem.
- /B - Blocks distribution
- /U - Unblocks distribution
- /H or /? - Displays the following summary help:
This tool can be used to remotely block or unblock the delivery of
Internet Explorer 8 via Automatic Updates.
------------------------------------------------------------
Usage:
IE80Blocker.cmd [<machine name>] [/B][/U][/H]
B = Block Internet Explorer 8 deployment
U = Allow Internet Explorer 8 deployment
H = Help
Examples:
IE80Blocker.cmd mymachine /B (blocks delivery on machine "mymachine")
IE80Blocker.cmd /U (unblocks delivery on the local machine)
------------------------------------------------------------
Group Policy Administrative Template (.ADM file)
The Group Policy Administrative Template (.ADM file) allows administrators to import the new Group Policy settings to block or unblock automatic delivery of Internet Explorer 8 into their Group Policy environment, and use Group Policy to centrally execute the action across systems in their environment.
After adding this administrative template to the Group Policy Editor, you must clear the "Only show policy settings that can be fully managed" option in the Filtering dialog before the new policy becomes visible in the Group Policy Editor. This option is found by highlighting "Administrative Templates", then selecting "View" and then selecting "Filtering". You will then see the policy under "Computer Configuration / Administrative Templates / Windows Components / Windows Update / Automatic Updates Blockers". This setting is available only as a Computer setting; there is no per-User setting.
Users running Windows XP or Windows Server 2003 will see the policy under Computer Configuration / Administrative Templates / Windows Components / Windows Update / Automatic Updates Blockers v2. Users running Windows Vista or Windows Server 2008 will see the policy setting under Computer Configuration / Administrative Templates / Classic Administrative Templates (ADM) / Windows Components / Windows Update / Automatic Updates Blockers v2. This setting is available only as a Computer setting; there is no Per-User setting.
Note: This registry setting is not stored in a policies key and is thus considered a preference. Therefore if the Group Policy Object that implements the setting is ever removed or the policy is set to "Not Configured", the setting will remain. To unblock distribution of Internet Explorer 8 using Group Policy set the policy to "Disabled".
Answers to Frequently Asked Questions can be found here.
Related Resources
- Internet Explorer 8 via Automatic Updates
- Internet Explorer 8 Blocker Toolkit FAQ
- Internet Explorer Product Site
- Internet Explorer 7 Blocker Toolkit Download
The Official fix worked for my Zune 30 but,
My wife’s Zune did not repair on January 1st so I thought I was going to have to buy her a new Zune but I found a solution.
If your Zune has a full charge disconnect it and let it die. Once your battery is depleted. NO NEED TO OPEN THE CASE. Hold the reformat command (Back Left Center). Connect the charger, keep holding the command until the device shows "Please Wait" or some variant. This is the initial cleaning phase. Follow the commands on the screen.
Let me say that it took me about 5 tries to get this to work and i needed my wife to plug in the Zune to my wall charger while i held the buttons.
You need to be a 3 legged Monkey to get this solution to work but it does work.
Once you get things working again and get the Zune reformatted you may need to have the Zune software “forget the device”.
Then add the device back again and resync your device.
Special thanks to the guys on this Forum post
http://www.zunescene.mobi/forums/index.php?PHPSESSID=6a46ab10528ec7b8a92e7aef3c124e0a&topic=43550.1134
Hope this helps others that are still stuck
Chris Stauffer <><