boognish

I am having this same exact problem and have tried a variety of combinations of schedules. No notification bubbles show.

Can an update be unexpired in SCUP and available for deployment again through SCCM? I set an update to unexpired and published but the update is greyed out in SCCM and doesnt deploy.

Does anyone know if it is possible to report on all aspects of a package, program, and advertisement in SCCM? A report showing the properties of packages, programs, and advertisements used for the purpose of documenting the packaging process. Source directory, command line, run from DP, all the tabs and options in a program and advertisement.

I saw that but Bits is set to not configured in the Computer Client Agent properties. "The first time it opens I think it starts the calculations on a 56k line, this is confusing. Then after it starts going it calculates based on the network and changes to 3 or 4 mins. Confirm that you see Estimated time to download XX hours X Minutes @ 56kps" Thats the issue...wish the calculation could be changed.

Is there a way to change the "Estimated time to download" for downloading a program? It is calculated at 56 Kbps. Management thinks people are going to freak out when they see this. A 215.5 MB program is reporting that it will take 8 hours 58 minutes This isnt my picture, just an example.

That's the way I have it set. I would assume that the toolkit files are loading because the shutdown.wsf is being called. My password would simply replace "password" in this, correct? If MyPass = "password" then env("ALLOWOSDBUILD") = "YES" End If

Thanks. I ended up creating steps to copy the usmtutil.exe and a batch file to the %systemdrive% and then run the batch file to delete the statestore.

Im getting the following error. Shutdown.wsf is in the TS password directory Cannot retrieve referenced URL : ..\ZTIUtility.vbs My TS is always aborting after i put in the password

Is anyone using usmtutils.exe during the task sequence to delete the OSDStateStorePath after a Hardlink? I know you have to use a batch file similar to "echo y| usmtutils.exe /rd %OSDStateStorePath%" but I am getting errors about UNC paths. I discovered the need to do this from this site. http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx

That would be great if its not too much work

My situation calls for using /md switch during the loadstate. I am having problems getting that to work. Is it still supported using hard link? My Value for OSDMigrateAdditionalRestoreOptions is /nocompress /hardlink /md:OldDomain:NewDomain

Is there absolutely no way to advertise an OSD task sequence to a AD security group of users? For example, if a company has group of Technicians that you want to advertise to so they can use them while out in the field. They would log in and be able to run the advertisement. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/dedf6a8d-a80c-4cf0-b169-2ff0532c4aa6#d1c15208-e1b5-4dfc-88c6-99c528ba6cdd

How long should the polling schedules be for AD system group, security group, and system discovery. My goal is to deploy software through AD Groups linked to collections. However I am getting duplicate records in SCCM during OSD. It appears that the polling schedules are messing things up. If I set the polls too long, clients wont get their advertisements after OSD for an extended amount of time. To short seems to put in duplicate records and they never receive advertisements. One record says MP_ClientRegistration Heartbeat Discovery The other says SMS_AD_SYSTEM_DISCOVERY SMS_AD_SYSTEM_Group_DISCOVERY For our migration we are prestaging computers in the appropriate OU prior to OSD. I assume AD discovery is finding the machine name prior to finishing OSD and adding it to the SCCM database. Then duing the task sequence the client installation is registering again.

Thanks, So in terms of deployment and managing systems, in a single site, no branches, there really is no added benefit to SCCM by having server 2008 R2... However if I had an MDT 2010 and WDS setup R2 would gain me the following. The following changes to Windows Deployment Services are available in Windows Server 2008 R2: * Dynamic driver provisioning. The ability to deploy driver packages to client computers as part of an installation, and the ability to add driver packages to boot images prior to deployment. For details, see Driver package provisioning later in this topic. * Virtual hard disk deployment. The ability to deploy virtual hard disk (.vhd) images as part of an unattended installation. For details, see .vhd deployment later in this topic. * Additional multicasting functionality. The ability to automatically disconnect slow clients and divide transmissions into multiple streams based on client speeds. Also provides support for multicasting in environments that use IPv6. * PXE provider for Transport Server. Includes a PXE provider when you install the Transport Server role service. You can use Transport Server to network boot, multicast data, or both as part of an advanced configuration. Transport Server is a stand-alone server. That is, when you use Transport Server for network booting and multicasting, your environment does not need Active Directory Domain Services (AD DS) or Domain Name System (DNS). For instructions, see the Configuring Transport Server topic. * Additional EFI functionality. Supports network booting of x64-based computers with EFI, including Auto-add functionality, DHCP referral to direct clients to a specific PXE server, and the ability to deploy boot images by using multicasting.

Im trying to figure out what benefits R2 adds to a SCCM 2007 SP2 environment. And if there are benefits what servers actually need to be R2. Any links or info would be greatly appreciated. Thanks. Site Server Management Point Server State Migration Point Server Distribution Point Server(s) Software Update Point Server