Migrating SCCM 2007 Secondaries to 2012 DP's and Contant Status is showing Unknown instead of Success

It looks like the packages converted with the DP and are being pulled from the client properly. When I went into Administration | Distribution Points the object "packages" at first did not show all the packages. After I scheduled a validation
they did show up. However the Content Status of the package is still showing Unknown. I've seen posts that others have had this issue. However I haven't seen the solution.
Help Appreciated!
Thanks

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

How to force site code discovery on all the clients, Migration SCCM 2007 to SCCM 2012

HI,
I migrated SCCM 2007 to SCCM 2012 SP1, but the clients does not update the New Site Code Automatically, if I click on Discovery option the client find the new site, but I need do this automatically because are too many clients.
This registry key does not exist on client computers.
HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min)
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour)
Any Help?
Thanks.

Hello ICH-CR,
Thanks for writing to the SysCtr ConfigMgr forums.
I think there are multiple solutions to this issue and you can choose whatever fits best to your scenario.
1. While upgrading the clients from SCCM 2007 to 2012 you can assign the clients to your ConfigMgr 2012 site.
http://technet.microsoft.com/en-us/library/gg682060.aspx#BKMK_AutomaticAssignment
You just need to ensure that you have a boundary group and boundaries. More details on
http://technet.microsoft.com/en-us/library/13694ac5-8f3b-42a9-8040-b23f21c79637#BMBK_CreateBoundaryGrp
I would suggest the first method because if you create another child site, you shouldn't have to reassign the clients back again. If that is unlikely then use the following script which is method no 2
2.
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327
This is a VBSCRIPT and can be ran from a network location using the PSEXC
3. Here is a smaller script
'Replace with your Site Code sSiteCode = "EnterNewSiteCode"
sMachine
= "."
set oCCMNamespace
= GetObject("winmgmts://"
& sMachine & "/root/ccm")
Set oInstance
= oCCMNamespace.Get("SMS_Client")
set oParams
= oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode
= sSiteCode
oCCMNamespace.ExecMethod
"SMS_Client",
"SetAssignedSite",
oParams
You can use this script as a logon script .
Anurag
Microsoft Certified Professional| Microsoft Certified Technology Specialist (ConfigMgr)
This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights.
My Blog
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.

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Migrating SCCM 2007 R2 database to SQL 2012

Am I able to migrate my SCCM 2007 R2 database from SQL 2008 (running in 2005 compatibility mode) to SQL 2012? Is it even supported to run a 2012 instance with compatibility set to 2005? Or will I need to upgrade the database at some point to get this to
work.
Currently, my attempts fail and the errors in the ConfigMgrSetup.log suggests an issue with compatibility:
Incorrect syntax near '99900'. : ins_upd
Incorrect syntax near '99901'. : ins_upd
-which led me to a hotfix (http://support.microsoft.com/kb/2676776) that, upon installing, indicated that it failed to completely install.
For whatever it's worth, the SCCM server is running 2008 x64 and the SQL server is 2008 R2.

See the caveats at http://technet.microsoft.com/en-us/library/ee344146.aspx listed under the SQL Server Site Database Configurations section:
"To use SQL Server 2012 to host the site database, you must install the following updates as described in the Microsoft
Knowledge Base:
Article 2676737
Article 2676776
Additionally, to use SQL Server 2012 for the site database, you must upgrade the instance of SQL Server in use at a site from SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012. It is not supported to install a new Configuration
Manager 2007 SP2 site with SQL Server 2012. It is also not supported to install Configuration Manager 2007 R3 when SQL Server 2012 is in already in use for the site database."
Jason | http://blog.configmgrftw.com

SCEP install and policy issue (after migration SCCM 2007 to 2012)

Hi,
We have some terminal services which were connected to SCCM 2007.
I migrated 3 of them (via "install client" in SCCM 2012), what worked fine. Since they become member of the Windows server group + terminal services group, they get the scep-client as well as a specific policy.
Now we have 1 terminal server which did not install the scep client.
Logfile:
Failed to get EP event code under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Failed to get EP event message under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
State 1, error code 0 and detail message are not changed, skip updating registry value   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
File C:\Windows\ccmsetup\SCEPInstall.exe version is 4.5.216.0.   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:52   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:02   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:12   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:22   43640 (0xAA78)
Unable to query registry value (ProductName), return (0x80070002) means EP client is NOT installed successfully.   EndpointProtectionAgent   21/08/2014 11:20:32   43640 (0xAA78)
So I installed the client manually via "SCEPInstall.exe /policy z:\client\ep_defaultpolicy.xml" (after a pushd \\sccmserver\c$\...client\).
2 things:
1.any idea why it wouldn't install "failed to get EP event code under reigstry key" ..?
2.specific scep terminal server policy will be applied afterwards (file exclusions etc), right (don't see it yet and refreshed policy several times)?
J.
Jan Hoedt

Hi,
I have seen a temporary solution, created a package with the command line: REG add “HKLM\SOFTWARE\Microsoft\Microsoft Security Client” and deployed this program to the Client.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Help me how migrate SCCM 2007 queries into SCCM 2012 queries

Hi,
I know query migration is not possible to 2012 SCCM. Any possible way ..?
Like powershell or script?

Hi,
These might be helpful for you to create your own script.
http://msdn.microsoft.com/en-us/library/hh949058.aspx
http://msdn.microsoft.com/en-us/library/cc145430.aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Site codes and migration from 2007 R3 to 2012 R2

Hi,
We have SCCM 2007 R3 in our environment with one standalone primary server in our main office, secondary server in an off site location and another distribution point in another location. My question is, If I build a 2012 R2 server and prepare it on a VM,
can I put the same site code on it or does it need to be different?
Basically, I would like them to run side-by-side and migrate slowly but surely or am I going about it the correct way?
Thanks,
Niall
Niall Carter

Agree with Jason, you need to use new site code.
For SCCM migration side by side, you can refer below link
http://scug.be/nico/2011/08/03/migrate-form-sccm-2007-to-sccm-2012-part-1/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCCM 2007 with MDT 2012 Update 1 - LTI Build Process - "UserLocale" setting is all lowercase.

Greetings all. I'm trying to resolve a situation where the "UserLocale" property is being set to "en-us" opposed to "en-US". Quick environment stats: SCCM 2007, MDT2010, using LTI build process with a
custom UDI. 2 Build Sites (customer build sites), both sites have branch distribution points.
Both sites are performing the exact same LTI builds. Same task sequence.
Both sites have MDT location records that have the "UserLocale" property defined as "en-US".
Both sites successfully build the same LTI build, but post build; Site A has correct UserLocale entry of "en-US", while Site B does not have correct UserLocale entry - it is set to "en-us". This wouldn't normally be a big
deal, however we have an enterprise application that is hard coded to look for case specific property of "en-US", so this application does not function as desired as Site B.
Both builds use the same task sequence, same OS.WIM (Windows 7 x86), and same unattend.xml. The unattend.xml does have UserLocale specified as "en-US" (and also the MDT location records for Site A and Site B both have "UserLocale"
property defined as "en-US", so I do not understand where the lowercase "en-us" is being populated from during the client build for Site B, when it works correctly for Site A?
Bdd.log for client build at Site A shows:
Obtained USERLOCALE value from SQL: USERLOCALE = en-USUpdated
C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-US (value was en-US)
Property USERLOCALE is now = en-US
Bdd.log for client build at Site B shows:
Obtained USERLOCALE value from SQL: USERLOCALE = en-US
Property UserLocale_Edit is now = en-us;0409
Property UserLocale is now = en-us
Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
Updated C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-us (value was en-US)
Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
Can anyone offer insight as to my next troubleshooting steps? I'm not sure why Site B, bdd.log - unattend.xml shows updating UserLocale to en-us instead of en-US?
(Please note I have verified that the OS.WIM, unattend.xml, and all MDT scripts that run during task sequence execution are exact matches on the BDP's for each site. Same size, date, and content)

Well, there must be something that is different... If you zip up the logs (all of them) from each setup, and mail them to me, I can take a quick look.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

SCCM 2007 Won't remove Distribution Points in Site Status

I'm working SCCM 2007 and have removed some orphaned Distribution Points by going through and removing any application assigned to them and then removing the roles under the Site Systems Folder.
The Systems then disappeared from under Site Systems but when I look under Site Status, they're still appearing in the list there and I have no option to delete them.
I've tried following this link (http://myitforum.com/myitforumwp/2012/02/10/removing-old-orphaned-site-systems-from-the-sms-and-configmgr-2007-database/) and changing their replication field from a 0 to -1 which removes them temporarily but they always return
into the Site Status.
I can't see them anywhere else in the console, they're definitely not sited under Site Systems so I'm a bit stuck and have 3 sites saying they're in a Critical State in Site Status because the Orphaned Distribution Points are still appearing there and I
can't see how to remove them.
To clarify, I removed the orphaned Distribution points over a week ago so I doubt it's something like waiting for the system to e them. I've tried rebooting the SCCM server and this has made no difference
My list of servers under Site Systems;
My Servers in Site Status;

Execute the following command on the database
Delete from DPinfo where server name like '%DPName%'
It is completely unsupported to delete anything from the CM07 database. Before doing this you should contact CSS directly for support and ONLY with their guidance should you perform this task.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 R2 - SQL query to know the compliance status of the client machines.

Hi All,
Can some one share the SQL query that will show the compliance of a "All systems" collection in SCCM 2007 R2 for past six months. I know that it is possible to get the reports from SCCM reporting but would like to run it from database.
Rgs,

In SQL queries used in the reports we have prompts and hence I wanted avoid that.
What wrong with either removing the prompts from the query or hard coding the prompt data?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 Query to compare two machines and their collections

I need a query/report in sccm to run against two machines. One has the base image and standard applications, the other will have the base image plus additional applications installed from the RAP menu. I'd like to query the two and find the difference
between their add/remove programs, and also add the Package ID.
I found this query below, but it doesnt display the Package ID, which I'd like to have as well.
Ultimately, I'd love the result to filter out the common aplications and only show what's missing from the base machine Vs the full-blown machine.
************* SQL STATEMENT BELOW HERE ************
SELECT one.Computer1Name AS [Computer 1 Name], one.Computer1Display AS [Display Name], one.Version0, two.Computer2Name AS [Computer 2 Name],
two.Computer2Display AS [Display Name], two.Version0
FROM (SELECT v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 AS Computer1Display, v_R_System.Netbios_Name0 AS Computer1Name,
v_GS_ADD_REMOVE_PROGRAMS.Version0, v_GS_ADD_REMOVE_PROGRAMS.InstallDate0
FROM v_GS_ADD_REMOVE_PROGRAMS INNER JOIN
v_R_System ON v_GS_ADD_REMOVE_PROGRAMS.ResourceID = v_R_System.ResourceID
WHERE (v_R_System.Netbios_Name0 = @Computer1) AND (v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 IS NOT NULL))
AS one FULL OUTER JOIN
(SELECT v_GS_ADD_REMOVE_PROGRAMS_1.DisplayName0 AS Computer2Display, v_R_System_1.Netbios_Name0 AS Computer2Name,
v_GS_ADD_REMOVE_PROGRAMS_1.Version0, v_GS_ADD_REMOVE_PROGRAMS_1.InstallDate0
FROM v_GS_ADD_REMOVE_PROGRAMS AS v_GS_ADD_REMOVE_PROGRAMS_1 INNER JOIN
v_R_System AS v_R_System_1 ON v_GS_ADD_REMOVE_PROGRAMS_1.ResourceID = v_R_System_1.ResourceID
WHERE (v_R_System_1.Netbios_Name0 = @Computer2) AND (v_GS_ADD_REMOVE_PROGRAMS_1.DisplayName0 IS NOT NULL)) AS two ON
one.Computer1Display = two.Computer2Display
ORDER BY [Computer 1 Name], [Computer 2 Name]

This is as close that I managed to get.....
SELECT one.Computer1Name AS [Computer 1 Name], one.Computer1Display AS [Display Name], two.Computer2Name AS [Computer 2 Name],
two.Computer2Display AS [Display Name]
FROM (SELECT v_Advertisement.PackageID, v_ClientAdvertisementStatus.AdvertisementID, v_R_System.Netbios_Name0 AS Computer1Name,
v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 AS Computer1Display
FROM v_R_System INNER JOIN
v_GS_ADD_REMOVE_PROGRAMS ON v_R_System.ResourceID = v_GS_ADD_REMOVE_PROGRAMS.ResourceID INNER JOIN
v_ClientAdvertisementStatus ON v_GS_ADD_REMOVE_PROGRAMS.ResourceID = v_ClientAdvertisementStatus.ResourceID
INNER JOIN
v_Advertisement ON v_ClientAdvertisementStatus.AdvertisementID = v_Advertisement.AdvertisementID
WHERE (v_R_System.Netbios_Name0 = @Computer1) AND (v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 IS NOT NULL)) AS one FULL OUTER JOIN
(SELECT v_Advertisement_1.PackageID, v_ClientAdvertisementStatus_1.AdvertisementID, v_R_System_1.Netbios_Name0 AS Computer2Name,
v_GS_ADD_REMOVE_PROGRAMS_1.DisplayName0 AS Computer2Display
FROM v_R_System AS v_R_System_1 INNER JOIN
v_GS_ADD_REMOVE_PROGRAMS AS v_GS_ADD_REMOVE_PROGRAMS_1 ON
v_R_System_1.ResourceID = v_GS_ADD_REMOVE_PROGRAMS_1.ResourceID INNER JOIN
v_ClientAdvertisementStatus AS v_ClientAdvertisementStatus_1 ON
v_GS_ADD_REMOVE_PROGRAMS_1.ResourceID = v_ClientAdvertisementStatus_1.ResourceID
INNER JOIN
v_Advertisement AS v_Advertisement_1 ON v_ClientAdvertisementStatus_1.AdvertisementID
= v_Advertisement_1.AdvertisementID
WHERE (v_R_System_1.Netbios_Name0 = @Computer2) AND (v_GS_ADD_REMOVE_PROGRAMS_1.DisplayName0 IS NOT NULL)) AS two ON
one.Computer1Display = two.Computer2Display
ORDER BY [Computer 1 Name], [Computer 2 Name]

MOF file migration from SCCM 2007 to SCCM 2012

Hi,
I have an issue while migrating SCCM 2007 MOF (Configuration.mof) to SCCM 2012,Problem is...
In our infrastructure, We have integrated our custom inventory classes with the logon script.Now we are migrating to SCCM 2012.When i migrate the same Custom inventory classes to SCCM 2012,I can able to compile/migrate, However SCCM 2012 views are not in
sync with SCCM 2007.
Example: If i use SCCM 2007 collection/Query in SCCM 2012 that uses these custom inventory classes, its thrown an error saying that objects in this query are not valid, because of this none of the collections/Queries that uses old inventory classes are not
working.
I dont want to change anything in the logon script...
Can someone please help me on this.Thanks in advance..
srkr

Hi Garth,
Thanks for the reply.
As per my understand,there's nothing to do with SMS_DEF.mof and only Configuration.mof can be editable.
When you say Importing sms_def.mof in SCCM 2012,I guess there's is something i missed out.
Below is the both SMS_DEF.mof and Configuration.mof from SCCM 2007, Also please let me know how to import SMS_DEF.mof in SCCM 2012
************SMS_DEF.MOF*********************
//-- SCCM Report: XXX_AD_Info
[SMS_Report(TRUE),
SMS_Group_Name("XXX AD Info"),
ResID(6200),
ResDLL("SMS_RXPL.dll"),
SMS_Class_ID("XXX|EDADInfo|5.0")]
class XXX_AD_Info
[SMS_Report(TRUE), key]
string KeyName;
[SMS_Report(TRUE)]
string Distinguished_Name;
[SMS_Report(TRUE)]
string AD_Site;
[SMS_Report(TRUE)]
string DCName;
[SMS_Report(TRUE)]
string MachineDomain;
*********Configuration.mof*******************
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
class XXX_AD_Info
[key]
string KeyName;
string Distinguished_Name;
string AD_Site;
string DCName;
string MachineDomain;
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
instance of XXX_AD_Info
KeyName = "XXX AD Info";
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Distinguished-Name"), Dynamic, Provider("RegPropProv")]
Distinguished_Name;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Site-Name"), Dynamic, Provider("RegPropProv")]
AD_Site;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|DCName"), Dynamic, Provider("RegPropProv")]
DCName;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|MachineDomain"), Dynamic, Provider("RegPropProv")]
MachineDomain;
srkr

Part of a migration project from SCCM 2007 to 2012 SP1 CU3 - Updates no longer working and reporting not correct

Been working on a migration from 2007 sp1 to 2012 sp1 cu3. I first installed directly to sp1 but realized we had a few 8.1 clients being built so I added the cu3 mid-stream. I moved over two small subnets and pushed out some clients.
I was able to push out updates from the 2012 server for OS realted updates to a collection. After CU3 I tried to do the same process with Office 2013 updates and it just seems to sit there with the enforcement state showing unknown in the report.
Also I checked the version of client on the machines and they have the CU3 version but when I run a report to show client versions it does not show these machines with the latest version but version for sp1. It's almost like my management point
is not working. (just guessing). I checked in the component status and everything is showing green. I tried a wbemtest on one of the clients in the collection for the targeted updates and that is coming back with acceptable results.
Not sure where to look next.
I am not real proficient in 2012 yet and still bumping my way along. Any help reviewing specific logs, etc. would be appreciated. I have been searching for a solotion for several days now.

Hi,
1.Please make sure the update deployment is show up on the Deployment tab(Assets and Compliance -> Overview -> Devices -> the specific client properties)
2.Check PolicyAgent.log on the client to see whether the specific client have received the deployment policy. If not, try to run the Actions about software updates on the Configuration Manager Properties from the client.
3.Examine UpdatesDeployment.log, UpdatesHandler.log. UpdatesStore.log on the client.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2007 to SCCM 2012: Failed Packages are reinstalled ??

We're going to migrate SCCM 2007 to SCCM 2012 (side by side).
On SCCM 2007 we have (for example): Advertisement "ADV1" that execute program "Program1" of Package "Package1". (example....)
What happend if a computer "PC1" is migrated to SCCM 2012 when execution result of "ADV1" on SCCM 2007 was failed ??
1) If I migrate only "Package001" and create a new deployment "Deploy1" to launch program "Program1" of Package "Package1 , by default, "PC1" is going to execute "Deploy1". I known it...
2) If I migrate "Package001" and "ADV1".....Will "PC1" execute "ADV1" on SCCM 2012 ???? This is my question
Thanks

Taken directly from Technet, Regards Damon.
Will
advertisements rerun after they are migrated?
No. Clients that you upgrade from Configuration Manager 2007 will not rerun advertisements that you migrate. System Center 2012 Configuration Manager retains the Configuration
Manager 2007 Package ID for packages you migrate and clients that upgrade retain their advertisement history.
https://technet.microsoft.com/en-au/library/gg682088.aspx

SCCM 2007 and 2012 Catalogs have a slight discrepancy when adding AR XI (11.0.10) update

SCCM 2007 does not display the Bulletin and Article IDs, whereas SCCM 2012 does. Can this be corrected for SCCM 2007as well?

Ben,
If you're referring to SCUP 2011 (Download System Center Updates Publisher 2011 from Official Microsoft Download Center), we are already using this in our environemnt. Yes... SCCM 2007 is supported by SCUP 2011.

Migrating SCCM 2007 Secondaries to 2012 DP's and Contant Status is showing Unknown instead of Success

Similar Messages

Maybe you are looking for