dylan93

Where do you find that error in the smsts.log ? The only error I could find was 0x80070057: <![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="11:19:07.647+240" date="06-19-2012" component="TSManager" context="" type="2" thread="1288" file="executionenv.cxx:426"> <![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="11:19:07.647+240" date="06-19-2012" component="TSManager" context="" type="2" thread="1288" file="engine.cxx:250"> Are you deploying to Windows XP ? If so then maybe this will help you.

Did you try to only use a computer name and see what System Center does ? Anyway, I tested it and yes it is possible, only provide the names in it like this: Name <NAME1> <NAME2> Make sure you have This file has column headings turned on.

Check your answer file: <![LOG[Failed to initialize answer file.]LOG]!><time="11:10:25.072+300" date="06-07-2012" component="OSDWinSettings" context="" type="3" thread="1084" file="osdwinsettings.cpp:363">

How do you deploy the unattended xml file ? For your second question, no you don't need to redistribute, because you point System Center to the source location of the package and not the file itself so it will use the file you specified in the Apply Operating System step simply from the source location used in the package.

We use secondary sites because all the clients should be managed by the primary site and secondary sites can be installed license free, we also use this hierarchy for easy management of all the sites. But its clear now, thanks for the explanations.

We do create everything on the Primary Site Server but we store the files themselves at the Secondary Site Server, what we don't understand is why the Secondary Site sends the files to the Primary Site.

Hello, This is our current hierarchy : 1 Master Server (System Center 2012 Primary Site Server) | \/ 1 Secondary Server (System Center 2012 Secondary Site Server) Everything works but we have a little problem understanding how System Center works. The Secondary Site Server stores Windows Operating System Installers for its own site and we created a image at that site that was saved at the Secondary Site itself, but when I want to add the image to the Primary Site Server so I can use it to create a Task Sequence for that specific site the Secondary Site sends the image file over the network to the Primary Site, why does it do this ? Can't it just create a pointer telling clients on which Distribution Point the image can be found and deploy it from there ? Since the clients are in the exact same network as the Secondary Server that would be the most logic option or am I doing something wrong ? We'd rather not have the Secondary Site send all the images and Windows Installation Files over the network since it blocks our complete network, we can throttle it or do it at night but that means our System Center progress would go very slow. Thanks

Because we don't want the server to download all the updates locally but we want the clients to download them themselves when appropriate from Microsoft and we want to be in control of what updates they should install.

Hello, I might have missed it or something but I couldn't find it on Google or on this site but I would like to know if its possible for the SUP role to have the updates for clients listed so the workstations contact the SUP server for the updates but downloads them from Microsoft and not from the SCCM server.

I have almost the same setup but I run on a ASUS N53SV-SZ404V with a Core i7 2630QM and 12 GB of RAM, all my VM's are stored on a 750 GB external harddisk.

The problem is, the machines are already deployed with an OS but they are not in the domain, hence the SCCM public share. But I guess Ican also redeploy them Nevermind that didn't read it right, well, that would require us to manually boot them into network mode or start from DVD... EDIT: Ok, I'm trying to use a task sequence to let the computer join the domain so I can advertise it through PXE boot, however I can't get it to work. This is the order of the TS: - Setup Windows and ConfigMgr (This is needed because the Windows installation doesn't have the SCCM client installed and is not part of the domain and so that the computer can reboot and resume the task sequence from within Windows ?) - Restart Computer to the currently installed default operating system. - Join Domain or Workgroup, join a workgroup WORKGROUP to make sure the computer is out of any domains ? - Restart Computer to the currently installed default operating system. - Join Domain or Workgroup, join the domain "test.local" with the "test.local\testadmin" account which is domain administrator. - Restart Computer to the currently installed default operating system. - Done ? However, after selecting the TS from the list and pressing next, it gets the setting and stuff from the server, I see the Setup Windows and ConfigMgr progress bar for 1 second and than it stops with the error code: 0x80004005 The client SMSTSlog.txt is attached... SMSTSlog.txt

Nobody ?

Hello, I was wondering if it is possible to run a SCCM Task Sequence from a share on the server on a fresh clean Windows 7/XP system that is not part of a domain. The thing I want to do is: On the local computer map a network drive e.g. and run a task sequence from the share created by SCCM that joins the computer to a domain, in MDT you can simply use something like net use * \\SERVERNAME\DeploymentShare$ /user:DOMAIN\ADMINACCOUNT cscript \\SERVERNAME\DeploymentShare$\Scripts\LiteTouch.WSF And it would list the task sequence in a menu within the OS, however I need this to be done in SCCM itself and not MDT.