Redistribute Configuration Manger Upgrade Package

Hi Guys,
Just some questions regarding this post (http://social.technet.microsoft.com/Forums/en-US/11df0f63-d146-434d-91f3-c4e826fee92c/redistribute-configuration-manager-client-upgrade-package-xxx00003?forum=configmanagermigration)
We are seeing a "Failed to update content properties" on all our DP's for the configuration manager upgrade package (XXX00002)
With the below PS snip:
Am I correct in assuming that this command will redistribute the upgrade package to all DP's?
"$SiteCode" should be the Primary server's sitecode even if we have a Central administration site in our enviroment?
Does anyone know what distribution priority the upgrade package is set to?
$SiteCode = "XXX"
$PackageID = "XXX00003"
     $distpoints = Get-WmiObject
-Namespace "root\SMS\Site_$($SiteCode)"
-Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
        foreach
($dp in $distpoints)
                $dp.RefreshNow
= $true
                $dp.Put()
Thanks in advance,
J.

Hi Torsten,
Thanks for your reply.
So run the Powershell command on CAS and use the sitecode for CAS here:
$SiteCode = "XXX"
And run your query to see the priority of the upgrade package?
Am I understanding you correctly?

Similar Messages

Configuration Manager client upgrade package failing to download to DPs

Hello,
I am receiving the following error in distmgr.log "Failed to get RDC signature path for for package SF100004 version 1. Error = 2"
"SF100004" is the "Configuration Manager client upgrade package"
Is there a way to rebuild/repair this package?

Yes, I did find out how to fix the problem. I had to use a power shell script to call WMI on the site server to manually force a refresh of the package having problems.
$SiteCode = "SF1"
$PackageID = "SF100004"
$distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
foreach ($dp in $distpoints)
$dp.RefreshNow = $true
$dp.Put()

Multiple duplicate Configuration Manager Client (Upgrade) Packages

We have 14x Configuration Manager Client Package / Configuration Manager Client Upgrade Packages in our SCCM2012R2cu1 environment.
We tried deleting all of the packages that were not linked to deployments/task sequences, but a few days later these were re-created with new PackageIDs.
Any ideas what could be causing this? are there some logs we should be checking?
http://oi61.tinypic.com/5nx4.jpg
Thanks!

FROM hman.log:
CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Handle auto-upgrade client configuration changes   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Update auto-upgrade client configurations   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
INFO: Full client package id XX1001EB exists.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade package id XX1001EC exists and upgrade package flag is set to 1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade program Configuration Manager Client Upgrade Program in package id XX1001EC exists and its currently disabled.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade advertisement id XX1203B8 exists for package XX1001EC and program Configuration Manager Client Upgrade Program. Deployment is targeted to collection SMS00001.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM
1936 (0x0790)
INFO: All client auto upgrade related objects exists. No objects are to be created.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Successfully added client upgrade packages XX1001EC and XX1001EB to all 31 distribution points from site XX1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
Wait for site control changes for maximum 3600 seconds...   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)

SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"

Hi Team; I’m having 2 issues with SCCM 2012 R2:
Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
distmgr.log file.
~Package BDC00002 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~SourceVersion (1) of package BDC00002. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~Package BDC00003 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002"
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
~SourceVersion (1) of package BDC00003. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
AVAL0="BDC00003" $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
the status is packages deployment compliance stuck at 0%
Infrastructure:
3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
server is configured for each group respectively.
A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
is that I can't deploy the packages to production PCs in the Office subnet!
Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
I tried configuring IP Subnet Boundaries, still no luck!!
Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
<![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
thread="4884" file="lsad.cpp:770">
And here are the last 4 lines in the ClientLocation.log
<![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
<![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
<![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
While on the PC that the application was installed on I see the folowing in the LocationService.log:
<![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
Is there something wrong with the Distribution point on the Secondary Site server?
Please help…
Thanks..

Update:
I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
However; the second issue is still unsolved...
Please help..

Unable to copy hidden package "Configuration Manager Client Package" to local DP

Content status lists it as successfully distributed to all DPs (including the local site server)
However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
NOTE: It appears to not be any of these causes.
If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
Intializing DP Monitoring Manager...    SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
distmgr.log shows the following:
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Retrying package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
No action specified for the package CDW00001.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Updating package info for package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Exiting package processing thread.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Used 0 out of 3 allowed processing threads.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)
Sleep 1825 seconds...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
http://support.microsoft.com/kb/811833) being enabled?
Nothing special with certificates; I've used the basic stuff for intranet management of clients.
The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
(as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

Creation of upgrade packages fails

Dear all
We did an upgrade from 4.0 to 2007, but now found out among other things that the MUP definition in the upgrade console was not updated. As such if we now want to create a new upgrade package with the predefined units (BOL, BDOc and UI) the creation of these units fails as some files are missing.
Does anybody know: Were the units redefined when upgrading to 5.0? And if so, how can I get my hands on one of these as I do not want to try and build the UI and BOL packages myself from scratch.
Thanks in advance,
Kai

Thanks Shankar,
The not does not apply (as 2007 SP2 which we are on is 5.0SP11 and the note is SP09 only), but via connecting notes I found the note 1156416 (did not help) and finally 1171933 which provided the correct solution.
Regards, Kai
Edited by: Kai Blanke on Jan 16, 2009 10:35 AM
Set question to solved

Windows 8.1 official offline upgrade package & GPO question related to Metro & UAC

Hello!
I am testing pre-deployment of Windows 8.1 in our 2008R2 domain. So far only my workstation is upgraded to win8x64 (from win7x64) and I am assessing if all of our LOB aps and servers will work fine with it. A few questions
1. We use workstations coming with OEM win8 license (all currently running win7 downgrade). I noticed that oficially there is no win8.1 offline upgrade package! Does that mean that Microsoft officially wants people to sing into Windows Store with a Microsoft
account to perform online upgrade with administrative privileges? That's pretty awkward ...
I figured that I could use win 8.1 installer ISO/UFD that I created in past (for home computer actually), but am not sure if that works out with our win8 OEM license keys tied to BIOS/UEFI on each desktop computer.
Was actually expecting an 8.1 Service Pack package that I could publish to WSUS, so it could take care of upgrade on win8 computers, but there is no such thing ... and no official package for 8.1 offline deployment either ... weird ...
Currently I am actually about to upgrade my own/test workstation to 8.1 (from 8.0, using Windows Store online), then sysprep it and create a reference WIM image and see if I can deploy 8.1 thick image (with all updates and company apps installed) this way
via WDS. anybody tested if it works this way? any gotchas?
2. win8 GPOs
Can somebody enlighten me where in Group Policies I can find a setting to re-assign ALL file/media extensions (e.g. jpg, tiff, png, bmp, mp4, WMV, etc.) back to Desktop applications instead of the horrible Metro UI equivalents?
We are actually about to bypass Metro UI completely on each computer so it boots straight to desktop and all file upon double-click must open an application within Desktop (no Metro UI for end users).
I know how to do this manually one by one via Group Preferences, but am asking if there is some specific GPO ADMX setting that would replace Metro UI apps with Desktop application in any and all file associations.
Personally I see no point in using the clunky Metro UI without a touchscreen.
3. is UAC enabled required for Windows Store to work?
Seems like it needs at least the Low security setting, so the Windows Store and Metro UI stays operational. no workaround for that for disabled UAC environment?
Just asking, it's not a big deal, people can learn to live with UAC, but am curious if that's by design.
Thanks for answers!

Hi,
1. For upgrading to Win8.1, please refer the following link:
http://windows.microsoft.com/en-in/windows-8/update-from-windows-8-tutorial As I know, Win8 activated using KMS, cannot upgrade to Win8.1
2. No, there is no such GPO settings added into Admin template. You will have to work around this using GPP...
3. There is no way to bypass UAC and allow Windows Store at one time. UAC is headache since Vista times and we have to live with the Protection :) Believe me, it does good to PC safety.
Regards, Brian
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
thanks for the answers!
Yeah, UAC is a bit of a headache especially with legacy software. When deploying our Win7 domain clients however I got away by simply disabling it to make it easier for all users coming straight from XP environment.
for future win8.1 deployments however, I will set the UAC level to Low and keep it there, so modern apps and winstore stays operational if anybody wanted it or needed it. not a big deal, plus an added security layer, I agree with that.
As per default win8 file extension associations ... well, that's a bummer, and yeah, the GPP is what I had in mind to work around that manually.
I am running on upgraded win8.1 right now and so far I like it more or less in work environment, after adjustments that is :)
My only problem is related to win 8.1 clean installation and imaging and deployment however, wanted to use Lite Touch via WDS for w8.1, but problem is that I have no image of win8.1 that can activate with OEM licenses tied to BIOS.
Sysprep doesn't work on upgraded 8.1 (from 8.0), so I can't image that with generalization and on other hand the only generalized image I can take is from bare win 8.0 without the 8.1 upgrade. What I mean is that our computer vendor (HP) switched to OEM
win8 licenses tied to UEFI/BIOS (no more case stickers) and that doesn't activate when I try to clean install 8.1 even though it should, but the build ID string in BIOS must be changed ... need to open a case with HP to work it out, I am sure it's still possible
to achieve even without volume licensing.
We use a Basic Infrastructure model so far with retail+OEM keys (no KMS so far but it's in plans if Office deployment plans get approved by CFO). I thought for 8.1 actually it was a good idea to implement Standardized Infrastructure with thick images, as
manual upgrade to win 8.1 from win 8.0 is painful.

No upgrade package found for component SAP_BASIS

Hello,
I'm just upgrading from NW 7.01 to NW 7.4. During the EHP_INCLUSION phase I'm getting this error:
The program has not found a matching SAINT package for 'SAP_BASIS'.
"Last error code set: Enhancement Package inclusion failed, no upgrade package found for component 'SAP_BASIS' "
I've checked the name of patches on stack.xml and upgrade directory, and patches are in the upgrade directory.
Any suggestion?
Thanks.

Hi Ruben,
From the error message
"Last error code set: Enhancement Package inclusion failed, no upgrade package found for component 'SAP_BASIS' "
You need to include delta upgrade package for SAP_BASIS component in the /EPS/in queue.
File name should be similar to "K-740BHINSAPBASIS.SAR". Please check whether such package has been downloaded ,extracted and include into the queue.
Hope this helps.
Regards,
Deepak Kori

Configuration and Business Package for Learning Solutions

Dear Experts,
I need informtion on the configurations and Business Package for Learning Solutions 2(business function HCM_LSO_CI_2) which comes with EHP4. We need to implement the LSO functionalities and I was not able to find out the required Portal Business Package. Please share your experience for implementation of LSO.
Regards,
Samir

Dear Experts,
Anyone already done LSO Learning Solutions implementation for Ehp4.Please provide inputs.
Regards,
Samir

Upgrade packages(mups) are not sent to ALL mobile clients

Upgrade packages are not sent to all mobile clients even though there are
subscriptions assigned. There are 3 sites(A,B,C) with these
subscriptions. Only one site(A) receives the package. The other two
sites(B and C) doesnt receive the package and their outbound queue doesnt
show the messages.
The subscriptions were earlier removed for these sites (B and C) and then
added back.
Generated all the bdocs in smoggen, gnrwb and sent the package again but in vain.

the generation did the trick. the queue has been stopped in between and that is the reason why the packages were not sent after the bdocs were generated.

Upgrading package billing question

Hello everyone, just registered, so this is my first post! (sorry it's so long)...
My query is this - I rang BT yesterday to upgrade to BT Unlimited Broadband (and to try to get a better deal, since we were still on the now presumably obsolete broadband option 2 at £23.80 per month!). Anyway, we were offered a great deal of £13.65 a month for the next twelve months which we were very pleased with. We had also been paying for the 'Unlimited Evening and Weekend calls' package on the phone (which had initially been free) but since we hardly ever use the landline and 'Unlimited Weekend calls' was being offered as a package with the unlimited Broadband offer, I asked for us to drop the Evening and Weekend calls subscription on the phone, which was agreed to. We also paid for a year's Line Rental Saver then and there for £141.
We had been paying quarterly up until now, but I was told that since we were starting a new contract, we would be changing to monthly payments, which I also agreed to.
All well and good.
However, due to very bad timing, our next quarterly bill was due to be issued that same day and, lo and behold this morning we received a pdf email notification with all our (few) phone calls listed (that's fine) and also the upcoming three monthly charges for 'Unlimited Evening and Weekend Calls' and 'Broadband, Option 2 - 40gb limit'. It also included the next three months line rentals, which of course, we have now already paid for in advance via the Line Rental Saver.
My question is this - will we still be charged for the next three months and then gain this back via a rebate in the September bill? I did call up BT this morning when we received this next bill and was told that it 'was wrong' and would be updated. However, as of right now, the bill is still there, charging us for the wrong packages and for line rental for which we have already paid. We were told that we would receive a letter in the post 'over the next few days' but the email we were promised yesterday confiriming our broadband upgrade and phone package change never materialised, so I'm a little dubious that it will arrive either!
Incidentally, when we log in our account (actually, it's my father's account, but I'm dealing with it for him), the correct, upgraded packages (Unlimited broadband and Unlimited Weekend calls) are listed, so I'm sure there's just some updating needing on the billing side. I wonder if I should contact them again or wait to see if the (promised) letter arrives and see what that says??...
Solved!
Go to Solution.

try online chat and see if they can clarify
live chat http://bt.custhelp.com/app/contact/c/2902/?s_intcid=con_intban_sanda_contact_us_chat_from_forums
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

HT1338 I cannot find the OS X Lion 10.7 upgrade package

For the life of me, I cannot find the OS X Lion 10.7 upgrade package. My mac mini is too old to go any higher, and I need iCloud on it. I need to get from OS X 10.6.8 to 10.7.

You have to call Apple store to buy 10.7 Lion.
They will send you a code via e-mail. That can be used to download Lion.
1-800-692-7753
Best.

How to deploy configuration manager client package to a query based collection

Hi
I have created one OU based collection.Now i wants to deploy client package to this collection so that the client automatically get installed,whenever a new machine added to the OU and so on to the collection.
But the issue is with configuration manager client package deployment,as we can't deploy the default configuration package to the collection(Deploy option is grayed out). For this i created a new configuration manager client package and deployed this package
to the query based collection.
Now when a new machine added to this collection,the client did not appear to deploy on this machine. Please help

If you want all the devices in the OU to get the client, you can use a Computer Startup Script to deploy it. Everybody just uses Jason's since it does everything and is well documented.
http://blog.configmgrftw.com/configmgr-client-startup-script/
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Client upgrade package

Hello,
I did a fresh install of SCCM2012 R2, for some reason I do not see CM Client Upgrade package in the Packages view, but see it in the Monitoring\Content Status with status that package was distributed to DP. Why? How can I recreate it?

That's a hidden package that won't show in the packages view.
If you need to recreate it, which is not really the case I think, you can create an empty file named
client.acu in the inboxes\hman.box folder at the top-level site. This will cause a new package to be created.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Upgrade packages from 2008R2 to 2014/SSDT2013

We are going to upgrade our environment from 2008R2 to 2014. This means both database engine and packages will be upgraded to 2014 and SSDT2013 respectively.
Has anyone experienced this scenario? Can you give me some advise or checklist before upgrading packages or if possible TSQL/store proc changes/testing.
How do you have done testing after upgrading packages for result scan (output comparison with 2008R2 packages)?
Any recommendation besides running upgrade advisor?
Thanks in advance! :)
ZK

Hi ZK,
Based on my research, some custom SSIS Tasks can always throw error after upgrading packages from SQL Server 2008 R2 to SQL Server 2014. After going thru the upgrade wizard you need to do several things:
Change your custom tasks and components to target the .NET 4.0 Framework in each of the project properties, in the Application Tab, under Target framework.
Update the assembly references in each of your projects to point to the appropriate SqlServer dlls.
Build and copy your project dlls to the appropriate directory, depending on what kind of components you are updating, i.e. Program Files (x86)\Microsoft SQL Server\120\DTS\PiplelineComponents
Register your components in the GAC.
Close Visual Studio and then reopen; open your SSIS packages and refresh the SSIS Toolbox, by right clicking in the tool box and selected Refresh Toolbox.
Besides, if some of your script task throw errors to you, we can open the script task in VSTA, insert Breakpoint to debug the scripts, then find the root cause. For more details, please see:
Debug a Script by Setting Breakpoints in a Script Task and Script Component
The following similar thread is for your reference:
http://nobrainerlab.com/2013/02/19/ssis-script-task-upgrade-to-ssis-2012/
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Redistribute Configuration Manger Upgrade Package

Similar Messages

Maybe you are looking for