anyweb

well what errors are you seeing ? is the device X86 or X64 ?

i'll post a guide about this soon (time willing) but in the meantime make sure you've got a backup of your database before starting and do a testdbupgrade on a copy of the database.

you need to find out what that package is (GR2000004) and update it to your distribution points

it should work with greater than 4gb, the keys i used in the above were 8gb in size

hi and thanks ! see my response below for details http://www.windows-noob.com/forums/index.php?/topic/6382-cannot-select-operating-system-installer/

what info did you enter on the Database Information page.

this is not a bug its a design change, when I wrote the initial guide RTM was released and SP1 was far from beta, in RTM you can select an operating system installer, in SP1 you cannot in the wizard but you can edit the task sequence afterwards to point to the intsaller if thats the way you want to do it, in SP1 the recommended way is to use the install.wim file either from a previously captured image or from the Installation media itself, this is the major design change in SP1.

then you are running an unsupported version, if you have any issues that require you to call Microsoft, Microsoft may not help you.

and how did you install it ? did you follow this guide ?

its on the CM server in the logs folder

SQL 2012 SP1 is not yet supported, see this post for details

no, currently as of today 29/1/2013 it only supports SQL Server 2012 currently (not sp1) see this post for details

hi all, i've been closely watching the growing number of views on both the Configuration Manager 2007 and Configuration Manager 2012 index of guides here, and now they've passed the 1 million mark today. I setup those index's to help people find content I created on windows-noob.com, the index's themselves just grew and grew both in content and popularity and today they finally got past 1 million combined page views. 1000343 page views ! Note: This is the number of times that those two posts have been viewed in total, it doesn't give us the total number of times all the Configuration Manager guides themselves have been viewed. You are more than welcome to click on the index's themselves to see how many times each guide has been viewed. here's some of the stats: The System Center 2007 Configuration Manager Guides http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/ 756,048 views as of January 28th, 2013. The System Center 2012 Configuration Manager Guides http://www.windows-noob.com/forums/index.php?/topic/4045-sccm-2012-guides/ 244,295 views as of January 28th, 2013. well I think that's pretty cool indeed, and here's to the next 1 million views ! cheers niall.

no i just want to know if you took a backup of your Configuration Manager database BEFORE you attempted to ugrade ?

its under the hood and in the process, see this post for details (long story short you can now point to install.wim on the installation media instead of using Setup.exe) in fact the new build and capture process forces you this way, here's an example of that (scroll down)

did you backup your Configuration Manager database before doing this ? can you post the entire log ?

have either of the servers been rebooted recently or had any antivirus software installed or gpo changes made that could exclude the DP share from being accessed ?

have any permissions changed on that server to cause the network path to be 'not found' ?

check your client.msi.log chances are you have this issue - http://support.microsoft.com/kb/2801987

is this Configuration Manager 2012 SP1 or RTM ? did it ever work ?

ok Zach, so you are deploying a MDT 2012 update 1 captured WIM file using Configuration Manager 2012 sp1 ? can you share the unattend.xml file here with others so that they may benefit, it would of course be nice if we could do this without having to capture the image outside of Configuration Manager, if i get time i'll delve into this (if i get time...)

Michael Niehaus talked about this recently on a mailing list and his comments are below:-

actually the updated code is just to correct the clients not getting deployed issue (which can be corrected by applying hotfix KB2801987) so if you have the earlier code and have applied the hotfix, then you don't need to do anything further, i've been impacted by this issue and it's easy to fix, the re-release of the SP1 code means that people will no longer have to worry about applying that hotfix. cheers niall

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'