[Collection change an deployment behaviour]

Thanks

[Collection change an deployment behaviour]

Hi Folks,

 

I have an application deployment advertised to a collection with direct membership to a security group that holds users account.

 

This works fine but we know this set-up could cause issues regarding licenses (software follows an users)

 

Client wants me to change membership from direct user security membership, to query security membership containing computers account.

 

My question is. Will advertise redeploy the application to the computers that has it already deployed?

Advertise is set to re-deploy if previous installation failed.

[SCCM 2007 Client Agent settings change]

Thanks!

[SCCM 2007 Client Agent settings change]

Do I need redeploy SCCM agent to all clients after I made any changes?

 

For example, if I add security group to Remote Tool Client Agent permitted viewers, when that will get applied?

After next client policy polling interval?

 

Thanks

Marcin

[Application deployment retry...]

Guys,

 

Adobe Reader failed to install on several system with an exit code 1603 - much saying "fatal error during installation".

 

I have set advertisement to rerun if failed previous attempt. How much time has to pass for the second attempt?

 

 

Thanks for a reply

[PXE boot - no entry in "Clear last PXE Advert"]

OK. I found something strange. Instead update current computer account in SCCM, another with the same has been created and old one has been marked as obsolete.

Can someone tell me why is that?

[Direct Collection and app deployment]

There is no such a log in SCCM 2007.

I have checked both users (C:\Windows\System32\CCM\Logs) and server location.

Even if you try to Google it all results are related to SCCM 2012.

[PXE boot - no entry in "Clear last PXE Advert"]

Hi guys,

 

I have created direct collection with several computers (Win XP). All of them have client installed.

I have created maintenance window and applied only to operating system deployment task sequences. The maintenance windows is from 1am today to 11om today.

That collection (lets call it "6thMay") is a child collection of "OS Deployment" collection. Task sequence is advertised to "OS Deployment" collection with option to include child collections.

 

Advertisement is set like that (see attachment):

 

Seems to be ok. Some PCs are already running task sequence and installing new OS.

Problem is while right click on the PC account in the "6thMay" collection that actually is in the middle of OS deployment, "Clear last PXE Advertisement" is empty.

Why is that?

[Server is a mess - rebuild or build new?]

I believe the licence is the issue. That is why he (me to) not goint for SCCM 2012.

 

I had similar problem. Customer got SCCM 2007 in really poor condition. I have deployed new SCCM 2007 server and I am moving all clients to that server. Removed boundaries in old one and will shut down in couple days.

[Direct Collection and app deployment]

Isn't the log present only in SCCM 2012?

[Direct Collection and app deployment]

OK. How can I change that?

[Numerous 5447 IDs in SMS_MP_CONTROL_MANAGER]

There are no duplicate GUIDs as the report "Computers that may share the same SMS Unique ID" shows nothing.

Bad certs? I have added RESETKEYINFORMATION=TRUE as the client parameter and pushed client installation again.

 

Let see if that helps.

[Direct Collection and app deployment]

Ath3na

What do you mean "If you are using application model"?

 

I have pushed SCCM clients install from new SCCM server to assign those system to new SCCM and I see that many applications are deployed again even if that application is already installed. Why is that?

[Numerous 5447 IDs in SMS_MP_CONTROL_MANAGER]

I will do that if they will appear as unapproved but they actually approved and I do not understand why I am getting those messages.

[Numerous 5447 IDs in SMS_MP_CONTROL_MANAGER]

Hi,

I have recently done migration from one SCCM 2007 to new one.

It has to be done as the old one was full of errors that it was beyond my knowledge to fix it.

 

After I have migrated boundaries from one to another, SCCM client has been pushed to the end points.

So far so good but I am receiving a tons of 5447 (MP has rejected a policy request from GUID:.......... because it was not approved. The operating system reported error 2147942405: Access is denied).

 

I have done my research and most solution I found saying that I need to approve those accounts.

 

I have run an SQL query to get a list of those accounts

Select distinct Name0

from [SMS_PRI].[dbo].[StatusMessages] as stat
left outer join [SMS_PRI].dbo.StatusMessageAttributes as att on stat.recordid = att.recordid
left outer join [SMS_PRI].dbo.StatusMessageInsStrs as ins on stat.recordid = ins.recordid
left outer join [SMS_PRI].dbo.v_StatusMessage as VStat on stat.recordid = VStat.recordid
inner join [SMS_PRI].dbo.v_R_System as SD on ins.InsStrValue = SD.SMS_Unique_Identifier0
join [SMS_PRI].dbo.ClientKeyData as CD on SD.SMS_Unique_Identifier0 = CD.smsID
join [SMS_PRI].dbo.v_RA_System_SMSAssignedSites as SAS on SD.ResourceID = SAS.ResourceID
WHERE (VStat.MessageId = '5447') AND
(stat.ModuleName='SMS Server ') AND
(ins.InsStrValue like 'GUID:%') AND
DATEADD(dd, 0, DATEDIFF(dd, 0, stat.Time)) >= '2015-04-22'

order by Name0 Desc

Then I have created collection to contain only those systems and all of them are approved.

 

How can I fix this?

Thanks

[Direct Collection and app deployment]

Thanks for the quick reply

[Direct Collection and app deployment]

Hi Guys,

Maybe you can point me to the right directions.

 

I have old SCCM server which is faulty and I am building a new one.

 

The company choose to deploy application to the users not computer accounts.

I have created a test collection "Deploy test app" with a direct membership rule to include AD security group "Test APP users".

I have created advertisement to deploy application to that collection.

 

As this is a deployment of new SCCM to production environment lots of the PCs already has that application installed.

My question is how to prevent that application be deployed to those PCs?

 

Thanks,

[Moving clients to different SCCM 2007 site]

I thought so. Will update this thread after the migration for future reference.

Thanks Peter.

[mdt join domain strange error]

I have the same problem when trying to deploy image of manually created reference PC and captured using SCCM 2007 capture media.

During joint do domain step in task sequence when domain name is domain.local, actually is attempting to join domain.local\dc.doman.local

Any one can tell why?

Reference PC hasn't been joined to domain.

 

OK. A short update.

Problem is gone. I have captured a reference PC image and that image have two data images: 1-1 and 2-2.

During deployment stage I have selected only second data image to be deployed and that cause a problem with joining to a domain.

I have deleted that task sequence and created a new one selecting to deploy all data images.

 

Be careful. I have no idea why but wizard is messing up whit the deployment task sequence steps. By default is trying to deploy 2-2 image onto next available partition. This will cause error. First partition is only 100MB in size.

To fix that move Apply Data Image 1 step before Apply Operating System Step. Then in Partition Disk step edit second partition and changed from fixed size to 100% if remaining space on disk.

 

This fixed my problem. Hopefully will help fix yours.

[Moving clients to different SCCM 2007 site]

Hi,

 

Ages ago someone deployed SCCM 2007 in our environment. I don't want to get into details about it. Simple saying it is not working as it should. It has't been patched updated etc. Total mess.

 

I have set up a new SCCM 2007 server, created completely separate SCCM site. Created boundary to be sure that those are not overlapping and works like a charm. Apps deploying without problems, OSD works too.

 

My question is, how quick and efficient move all clients from old SCCM site to the newly created?

My first thought was to uninstall SCCM clients and then extend boundary of new SCCM and push client installation from new server.

Is this good approach or there is other, maybe simpler way to do that?

 

Both SCCM server has to work at the same time during the transition.

 

There are hundreds PCs so going from one to another is not an option.

 

Thanks.