oxyle

Solved! Turns out the ISP was handing out IPv6 DNS servers inside hes local network. He blocked that in the modem and all of the machines started resolving locally on hes DNS server the management point now! Would have been the last place where I would check... Kind Regards, Kevin

Dear IT'ers, A friend of mine ran into an error that is getting really annoying right now. Every time when we install hes lab environment, we keep running into 0x80072ee7 during an OSD deployment. We've done the following: Reinstall the whole environment from scratch. Install a single stand-alone primary site. We've verified the DNS records were made. We've applied CU3 to SCCM before doing anything else in the console. Applied boundary groups Installed the PXE role, and verified that WDS was running. Now when we start a clean Hyper-V Gen1 machine with a legacy NIC we run into the error above... The VM gets an IP...(During networkboot) The VM can ping everything in the local network. It can ping the SCCM/DNS server on name. However when we try to ping the FQDN of one of these machines it would fail. I've attached the smsts.log to this post. Hopefully you guys can help! Kind Regards, Kevin smsts.log

Does anyone has an idea?

Hello guys, Since yesterday I've been starting to use Configuration Items around in ConfigMgr. But I am running into a challenge that I would not know how to fix right now. We currently have 2 (Local) accounts within our image. So the computers I am talking about are not members of any domain. An account with administrative privileges to which this does not problem applies to. An "normal" (Student) accounts, with no administrative privileges, to which this problem DOES applies to. I've created a Configuration Item with the following settings: General tab: Hivename: HKEY_CURRENT_USER Key Name: Software\Microsoft\Windows\CurrentVersion\Policies\System Value Name: Wallpaper Unchecked: This registry value is associated with a 64-bit application. Also by default this key is not found by default in this part. Compliance Settings tab: The settings must comply with the following rule: Equals :C:\Windows\Web\Wallpaper\Windows\img0.jpg Checked: Remediate noncompliant rules when supported. Checked: Report noncompliance if this setting instance is not found. However the above settings do NOT get applied when I'm manually running it on the student account. But the registry entry in HKCU\Control Panel\Desktop\Wallpaper will get applied when using Student account. It seems like a permissions issue to me, but I just don't know where to look when using these Configuration Items(which are pretty new to me). Kind Regards, Kevin compliance_report.htm

I think Niall has a pretty good answer/guide to your question here, http://www.windows-noob.com/forums/index.php?/topic/5605-using-system-center-2012-configuration-manager-part-3-configuring-discovery-and-boundaries/

You should update the SQL server you have installed earlier. Please consider the following table. "Configurations for the SQL Server Site Database" http://technet.microsoft.com/en-us/library/gg682077.aspx Determine wich version of SQL Server you have running and update it before running the ConfigMgr installation wizard again. The following link will take you to one of the Technet SQL Pages containing all the versions/updates you'll need. http://technet.microsoft.com/en-us/sqlserver/ff803383.aspx

Alright! Nice find, let me know what the results are.

Im not sure what to do now, since I've used up all my ideas. Last link that I found for you: http://social.technet.microsoft.com/Forums/en-US/29135ae5-5f0c-49d9-b7ad-f4d5e9664a33/sccm-2012-sp1-sup-on-windows-server-2012?forum=configmanagerdeployment Poeple saying this is what helped them: Kind Regards, Kevin

Your SQL server needs to contain a fully installed instance before you can update it. Did you already installed a instance for ConfigMgr? If not, do that first and then run the SP1 update again!

You might want to wsustil.exe then. WSUSutil.exe is located in the %drive%\Program Files\Update Services\Tools Here's some documentation about it: http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx

Did you integrate your SCCM/WSUS server with System Center Updates Publisher? I also saw you are running a 2008 (R2) version of WSUS. Did you verifiy you got both updates for it? (min WSUS 3.0 SP2 + KB2720211 + KB2734608) Link to both updates: http://support.microsoft.com/kb/2720211 http://support.microsoft.com/kb/2734608 You also might want to look in the event viewer of Windows itself, WSUS might be spitting out some errors over there.

Could you post your WCM.log and WSUSCtrl.log file too, please?

Did you check your network utilization/CPU/HDD(also on the database server) in the morning? It might be able to get you going in the right direction.

Hello, Maybe you should check this link out to get u started: http://helpdesk.illinoisstate.edu/kb/1875/Software_Packages_and_Applications_in_SCCM_2012/ Kind Regards, Kevin

Did you check out the maximum run-time of the created application? You can check it by going to the Deployment Type of the specific application and go to the tab "User Experience".

You could try to add the SCCM computer account to the local administrators group on the WSUS server? In our environment the WSUS is running on our CAS server, and the 2 other primary sites retrieve their updates from it. Did you run the post installation wizard on the central site aswell? I didn't the first time, and ConfigMgr could not connect to the WSUS server. After I ran the post installation wizard(Not the configuration Wizard) it started to connect succesfully. Maybe you'll benefit from the picture below: Also the log is saying that the remote configuration failed to server: 172.31.36.61, is this your ConfigMgr or your WSUS server?

Not sure if i understand you correct. You want to run a specific script to a user that's currently logged in? Maybe this helps? The picture below is taken at the properties of a program inside a package. If you put %username% in the script, and execute it while the user is logged in it will fill in the blanks. Good luck!

I fixed this by adding a value to the unattended installation file(.MSP) with "Setup.exe /admin". Just follow one of the above guides, and add this extra line to it. It will automatically activate the products! Just don't forget to update your Distribution Points.

What version of Configuration Manager are you running? If your running 2012 R2 please verify that the WDS service is running and started. There's also a hotfix available from Microsoft, but please read the notes before installing it. http://support.microsoft.com/kb/2905002/en Good Luck!

After you've approved the computer you can also restart the SMS Agent Host service withing Windows on your client. Or you could just check for new Computer Policies(Control Panel > Configuration Manager > Actions).

Is the client approved in the ConfigMgr console? Or does it even show up at all? You can check that under Devices(Collections).

Also after you've install the client as Peter suggested don't forget to manually "Approve" the client in the ConfigMgr Console.

You can find the log files for the client during OSD in the following location. Before the HDD formats: "x:\windows\temp\smstslog\smsts.log" After the HDD formats: "x:\smstslog\smsts.log" After the OSD applies the OS they are often located within "C:\Windows\CCM\Logs".

Hello, I've seen this exact same behavior during my Task Sequences with the same '&' sign in it. You could also create a package with all the commands in a .cmd/batch file. And then just run that package during your Task Sequence. I tried the exact same powercfg configurations during the Task Sequence, but it didn't work out. You can also set Power Settings in the Device Collections, just right click on them and go to Power Managment. Kind Regards, Kevin