anyweb

did you try this yet ? http://www.windows-noob.com/forums/index.php?/topic/3890-using-sccm-2012-beta-2-in-a-lab-part-4-application-installation/

i've just tested importing the Task Sequence on a console with SCCM 2007 SP2 R3 and MDT 2010 integrated, worked no problem. I don't have a SCCM console without MDT integration to test with so maybe that's it...

got it in the post yesterday and here it is !

follow the guide instead, then tell me what fails.

and where are you getting the error above ? at what stage in the Build and Capture process was it ?

are you testing with SCCM 2012 beta 1 ? you do realise that beta 2 is out now and is the current version ?

and if using a .VBS file try the following Dim oTSProgressUI Set oTSProgressUI = Wscript.CreateObject("Microsoft.SMS.TSProgressUI") oTSProgressUI.CloseProgressDialog()

check to see if this computer is in an ou targetted with any other software updates (eg: wsus gpo) if not, check the actions tab of the client, are all actions present ?

check the following folder on the client c:\windows\ccm\logs anything in there ?

verify that your boundary group is assigned to your site

are you sure you are using that boot image in your task sequence ?

have you seen this post from Chris ? http://myitforum.com/cs2/blogs/cnackers/archive/2011/09/09/configuration-manager-hydrating-secondary-sites-with-configmgr.aspx

remember this is beta, and the EULA states you should not put it in production, but sure, in a lab go ahead and test a migration, post your results/questions here

contact me at my email anyweb AT hotmail DOT com and i'll start the ball rolling

well just keep them in separate test environments, dont have overlapping boundaries and dont push the client, should be fine

what does the smspxe.log reveal about the probelm when you pxe those affected computers (hint: search for the mac address of the computer and not the messages)

I'm extremely pleased and very proud to have received this mail in the post today, I'd like to share part of it with you:- Huge thanks go out to my Family for supporting me and to my MVP colleagues for their support, and to my employer for supporting my efforts (Enfo, Zipper) and last but not least Microsoft for re-awarding me this covetted title. cheers ! niall

so you created a package in SCCM 2012 beta 2 ? and are trying to deploy that ? or an application ? please tell us more about what youve done, and how

i'm happy to do a remote desktop session to your setup to look at it, perhaps you've missed something, i can do vnc/remote desktop (mstsc)/teamviewer or others just let me know

well it's a bit confusing but we'll get used to it soon enough, to add to this, when you get to Deploying applications in a Task Sequence (for OSD) you'll see that the application will need a deployment type for this application and that the deployment type should be set to Install for System or Install for System if resource is device; otherwise install as userotherwise the application will not be able to be added to the Install Applications step

check the package status, is it listed as installed on the distribution point ? also, did you configure the network access account ?

hi Dan, thanks for the kind words ! i think the Technet documentation is actually fantastic but it's not all there obviously, however in relation to what you are asking see below (from Technet, how to create an Application) Install for user or System – Specify whether the applications deployment type will be installed for the currently logged on user or for all users. You can also specify that the deployment type will be installed for all users if it is deployed to a device or to a user only if it is deployed to a user. Configmgr 2012 application installation is all about the User so in the examples above we are just experimenting with the different options available to us, as regards Deployments yes some settings are not changeable after they are created (like most of the deployment settings, some of the general settings like collection/software), perhaps this might change in future releases i don't know

post the smsts.log file here so (from the client)

hmm are you deploying to virtual machines or real hardware ? sounds like a network driver issue, do you get an ip address ? can you ping the fqdn of your SCCM server ?

if you look at the task sequence i've supplied there is a network connect step, and that must occur (it maps to a drive letter) before you can store anything on the network, below is the XML from the step in the task sequence itself, just import the TS into configmgr and you can see the step yourself -<step name="Connect to Network Folder" description="This step is needed otherwise we cannot display any stored States in the Bare Metal/New Computer scenario" successCodeList="0" runIn="WinPEandFullOS" type="SMS_TaskSequence_ConnectNetworkFolderAction"> <action>smsnetuse.exe %SMSConnectNetworkFolderPath%</action> -<defaultVarList> <variable property="DriveLetter" name="SMSConnectNetworkFolderDriveLetter"> Z:</variable> <variable property="Password" name="SMSConnectNetworkFolderPassword"> </variable> <variable property="Path" name="SMSConnectNetworkFolderPath"> \\sccm\USMTStores </variable> <variable property="Username" name="SMSConnectNetworkFolderAccount"> server2008\sccmnaa </variable> </defaultVarList> </step>