anyweb

i'm seeing the same thing, still investigating....

and unfortunately that log doesnt contain the failure either, as you are downloading content from the dp instead of accessing it directly, therefore every time you download a file it's logged about three times, filling up the log with info we don't need as your problem is related to capturing, check the network share, do you have access to write to it ? check the permissions of the account assigned to that step, can they write, do you have the possibility of doing a teamviewer session with me to show me the issue, perhaps i can locate the problem as it's difficult to explain log 'hunting'

The binaries for System Center Configuration Manager 2012 and System Center Endpoint Protection 2012 have been updated to correct some minor issues. The binaries have been updated at the Download Center, and also on the Technet and MSDN download sites. For Configuration Manager 2012 SP1, the updated download release of SP1 includes the following hotfix: Installation error 0x800b0101: System Center 2012 Configuration Manager Service Pack 1 client http://support.microsoft.com/kb/2801987 For Endpoint Protection, the new binaries include fixed files (Linux/iOS) that were corrupt in the initial release. MSDN Download Link: https://msdn.microsoft.com/en-us/subscriptions/securedownloads/hh442898#FileId=52479 Technet Download Link: https://technet.microsoft.com/en-us/subscriptions/securedownloads/hh442904#FileId=52479 Microsoft System Center 2012 Service Pack 1 Configuration Manager - Clients for Additional Operating Systems http://www.microsoft.com/en-us/download/details.aspx?id=36212 This means if you downloaded the binaries prior to today (1/25) - you will likely need to re-download them. source > http://blogs.technet.com/b/gladiatormsft/archive/2013/01/26/you-may-need-to-re-download-configuration-manager-2012-and-endpoint-protection-2012-sp1-binaries.aspx

Successfully completed the action (Partitionner le disque 0) with the exit win32 code 0 that's the last thing in the log, check for another log called SMSTS*.log the date and time will be in the *

you need to capture the SMSTS.log (from the client) before it reboots, so press f8 during the installation and when it fails copy the log to usb stick and post it here

have either of you configured anything in relation to pull dp on the properties of the dp?

thanks, the maintenance windows post will come in the future when i get time, but the next post i've planned is for updating the CAS/Primaries/Clients to SP1, so please be patient, each and every guide I do can take days of work and it's all done in my spare time...

lets do it tomorrow i'm way too tired now, send me a pm with your email and i'll contact you tomorrow and we can do a session

ok so did you have a WDS server/service running on this box already, and simply re-used that WDS service for ConfigMgr ? do you have any possibility of remote access so that I can see your desktop, Team Viewer works well for me

take a step back first and verify that you've enabled PXE properly in three places look here - and verify you've done all those things

what do your logs tell you ? (you may have to repeat the process again)

are you a local administrator of that server ?

what extra content was it trying to add ?

the guides here have been for setting it up in a LAB, so in a lab environment having multiple roles installed on one box is acceptable, in production you'd definetly want to separate out those roles and have AD on one server (domain controller), Configuration Manager on another and so on I hope that clarifies it for you

try it and see what happens

EndPoint Protection can uninstall the following products automatically, however you'll have to configure the client settings in order to make this change. Select True (Configuration Manager with no service pack) or Yes (Configuration Manager SP1) to uninstall existing antimalware software.

you can't change it, you'll need to create a new deployment with the new purpose (required or available) and if you don't want the previous deployment, delete or disable it.

have you tried disabling any antivirus solution before doing this ?

thanks i'll update my post to reflect that info.

Ever since the Surface RT launched, we’ve been anxiously awaiting the debut of its big brother, the beefier, Windows-8-Pro-running Surface. In late November, Microsoft finally revealed pricing data for the Surface Pro, but we still didn’t have a firm date for its availability, beyond sometime in January. Well, we’re deep into the month at this point, with no sign of any new Surface models; what gives? Today, Microsoft provides the Surface Pro a release date, and while it’s going to miss that January window, it won’t be by much: the Windows 8 Pro Surface will go up for sale on February 9. This time around, the tablet will have broader retail availability from the start, and will be sold by Best Buy in Staples in addition to Microsoft’s retail and online stores, in both the US and Canada. Like we heard before, the 64GB model will sell for about $900, and the 128GB version will go for just under $1000. In addition to the new Surface, Microsoft also announced some new laser-etched limited edition Touch Covers, and a Surface edition of its Wedge Touch Mouse. via > http://pocketnow.com/2013/01/22/microsoft-surface-pro-date

it get's updates based on the settings defined in the antimalware policy that is targeted to collection(s) it is a member of, so if it's not in a collection targetted with the above (and client settings to enabled endpoint protection) then it won't take them from configuration manager

SQL Server 2012 SP1 is NOT SUPPORTED at this time see http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq and screenshot. as regards the bgb error try running this command lodctr /r followed by a reboot and then retry.

apart from the fact that SQL Server 2012 SP1 is not supported, disable any antivirus software you have and try and the installation again.

it's available on the MSVL sites now http://www.niallbrady.com/2013/01/15/system-center-2012-configuration-manager-sp1-is-released/

did you read the guide ?