ercole77

Hi, 2 questions 1) in a production environment is correct to use BULLETTIN ID=MS? In other words, are all the security patches included in MS bullettins or am i missing something ? 2) Im going to create this: a) a compliance group (not deployed) with all the patches (more than 1000) b ) one or more updates group deployed to all systems for past patches c) ADRs for monthly patches Compliance group must be deployed and disabled or not deployed? Many thanks for your guides !

reistalled MP role, now all is working

same problem here....did u find a solution?

Hi Ronnie, can you tell me how you solved if you got it? Same problem here. I found an implication with Mcafee Viruscan i have installed on primary site server. Disabling on access scanner resolve the problem, buti at the monent i dont know what i have to exclude

ok perfect good to know

hi Tmiller i solved; tasks with problem were configured to use a x64 boot image. I noticed that pxe boot with x86. Changed task image to x86 and message disappeared. Is it normal for pxe to boot only with x86?

Hi guys i have this strange beahviour on my SCCM2012 task sequences. Client boots to PXE, i insert pwd to access tasks list, select a task and after a while i see "Ready to start. Remove the cd and do not boot from cd" It's annoying because i have to click continue. How can i get rid of this warning? Don't know why it appeared

Solved, i disabled Active directory system discovery and added to task sequence this script to forc a cycle actionNameToRun = "Request & Evaluate Machine Policy" Dim controlPanelAppletManager Set controlPanelAppletManager = CreateObject("CPApplet.CPAppletMgr") Dim clientActions Set clientActions = controlPanelAppletManager.GetClientActions() Dim clientAction For Each clientAction In clientActions If clientAction.Name = actionNameToRun Then clientAction.PerformAction End If Next Now works like a charm. Thanks to everyone!

Makarovs im going to install wsus role on my sccm 2012 exactly as you did: i alredy have a separate WSUS on 2008 R2 sp1, when you installed sup, did it aske you to provide remote wsus info?

for 64 bit i have found http://jackychuasce.blogspot.it/2012/05/why-click-on-tsmbautorunexe-cannot.html it works but my problem is how to capture a 32 bit, wizard does not start

same situation it doens work

found description of the problem http://blogs.technet.com/b/configmgrteam/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx So i received duplicate record because i had these OU - OFFICE1 (inside department OU) - OFFICE2 (inside department OU) - DEPLOY Deployed PC go in DEPLOY OU. Active directory System discovery was set to these 3 OU so a record was created by this and another by hearthbeat discovery. Now i have deselected AD system discovery on DEPLOY OU so duplicated pc are avoided. The problem is: after a new pc is deployed i need to manual perform a cycle to make pc appears in asset. What's the best way to avoid this?

Ok Peter thanks but how much time does it take to delete duplicate records? Many thanks for your help

disabling automatic update i have no error in ccm.log but still duplicate entries

here is ccm.log during client install on a client. I have verifyed DNS and reverse lookup. During the install i executed pressing F8 "netsh firewall set opmode disable" Without firewall it works but i have duplicate id in console, one with client installed YES and nother with client installed NO ccm.log

Im going to check if admin$ share is reachable during sccm client deployment. Is there something about firewall i can verify? I cannot ping the client at this moment during this phase if the task.

hi thanks for your reply. Yes i created the configclient package exactly as that useful guide says. Installation was perfect, and i can see SITE code correctly; i performed domain join. Now i have checked and unknow client disappeared, i see one MININT-xxx with client installed yes and another MININT-xxx (the same) with client installed no. I think im missing something or something goes bad when client is deployed. I cannot get rid of this error -> ERROR: Unable to access target machine for request: "2097152087", machine name: "MININT-KU3QBND", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:52 4724 (0x1274)

another UPDATE......during deployment if i press F8 i can ping hosts by name and by ip. BUT i cannot ping the deploying machine itself from other hosts. Name is registered in DNS and regularly resolved but machine is not pingable..cannot understand WHY

UPDATE in ccm.log i have ---> Attempting to connect to administrative share '\\MININT-KU3QBND\admin$' using account 'domain\account' SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:09 4724 (0x1274) ---> ERROR: Unable to access target machine for request: "2097152087", machine name: "MININT-KU3QBND", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:52 4724 (0x1274) i changed sensitive info with domain\account but this is a domain admin how is possible it cannot connect to admin$? ..

Hi guys i have this problem with SCCM deploy phase. A deployment to unknow computers using PXE...the process begins, and i see a "unknow" computer under SYSTEMS. When all is done i see the final computer name MININT-* with client installed NO and inactive but the UNKNOW computer still remains on the console. Looks like the unknow has to be renamed or something else but doesnt occour. On the just deployed client itself i see only few Actions under Config mgr client. Am i missing something?