Jump to content


anyweb

How can I deploy Windows 8.1 using System Center 2012 R2 Configuration Manager

Recommended Posts

try x:\windows\temp\smstslog\smsts.log

 

is that different ?

Share this post


Link to post
Share on other sites


I cant check that anymore since i have messed up the client.. But I now have removed Apply Data image from my task sequence, and now its a few steps further during the osd.

 

When I create a task sequence with my captured .wim file I get apply operating system and apply data image.

I also tried with install.wim from the dvd. When I create a task sequence with the install.wim there is no apply data image at all..

 

 

EDIT: the OSD is now finished and windows 8.1 is installed. What does the apply data image do or not do.. Apperently I dont need it? So why does it appear in my task sequence?

Share this post


Link to post
Share on other sites

Bump on the question about what the "apply data image" does in a captured image. Do I need it or should I always remove that from my tasksequence?

Share this post


Link to post
Share on other sites

it all depends on the captured WIM File, if you don't need the apply data image step, don't use it, I don't use it for my production windows 8.x task sequences with only one index in the captured wim.

Share this post


Link to post
Share on other sites

I have currently 3 distributions points. I want to know how I can make sure clients connect to the correct distribution point. The way it is now that 2 out of 3 distribution points are randomly chosen.

Share this post


Link to post
Share on other sites

define your boundaries and boundary groups correctly and add dp's to the correct groups

Share this post


Link to post
Share on other sites

192.168.1.* is my primary site, site server and first DP

192.168.25.* is my second site system, DP

192.168.30.* is my third site system, DP

 

For testing purposes I have deleted all my boundries and boundry groups.

I created 1 new Boundry group: At references content location I chose the distribution point that resides inside the 192.168.1.* range

I created 1 new boundry: Type IP address range 192.168.1.20-192.168.1.250, add boundry groups I chose the just created groups.

 

When I boot a client that resides inside my boundry it still goes to my second DP instead of the first (the one it should be choosing)

 

What am I not doing right with boundries.

 

(I also think these question should not be in this post, srry for that)

Share this post


Link to post
Share on other sites

I have SCCM 2012 R2. I have been deploying 8.1 to various Dell Latitudes 'in house' with success. I am now trying to deploy the SAME task sequences to a remote location using a distribution point. Boundaries/boundary groups are set up. The task sequence errors out almost immediately with 0x8022001B. The first step in the task sequence is to boot into Win PE, this is where it fails.This laptop (Dell E5430) is wired in on the network and I am able to access it with no issue. Keep in mind, I have used this task sequence successfully on multiple 5430s in house. Distribution points show OK status in SCCM.

 

Does anyone have any thoughts on this.

smsts.log

Share this post


Link to post
Share on other sites

does it fail after the boot to WinPE or while still in windows ? if it's while in WinPE then have you verified that it actually has an ip address and can ping the fqdn of the management point in winpe ?

Share this post


Link to post
Share on other sites

After I deployed windows 8.1 I always have exclamation marks at usb-controllers in Universal Serial Bus-controllers. The drivers are present on the machine. If I click on update driver, search my computer and then choose drivers from a list from my computer and choose the driver there it installs and works. But I assume this is something i shouldnt have to do. Is there something in the TS that i should do?

Share this post


Link to post
Share on other sites

post-31474-0-59381000-1443723541.jpgGreat post.... I have a question though :)

 

I have created a custom task sequence for Win 8.1 Ent. x64 and created bootable media which I am using to image a VM in Hyper-V (See attached). The Install Windows 8.1 x64 task sequence installs and then just boots into the OS and doesn't even move on to the next series of task sequences??

 

 

 

Share this post


Link to post
Share on other sites

you need to look at the smsts.log file to determine what step is failing (and why it's failing)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...