mrbios

Hi, I've followed this guide: https://www.andersrodland.com/deploy-net-framework-4-6-2-with-sccm/ to deploy the .net framework as an SCCM application, it works perfectly when i deploy it to machines outside of an OSD TS, but when deployed as part of a TS it appears to get stuck for ages, then does a forced restart (no countdown, just cuts off the TS process) then loads up into windows without continuing the rest of the image. Anyone have any suggestions on a solution for this? EDIT: typical, this problem annoyed me for 2 days, soon as i put a thread up for help, i find the solution. I just had to tick "Run installation as 32-bit process on 64-bit clients"

http://techwithandrew.blogspot.co.uk/2013/06/getting-401-authenitcation-issues-on.html http://www.windows-noob.com/forums/index.php?/topic/6723-os-deployment-errors/ http://venusingireddy.blogspot.co.uk/2013/08/401-authentication-failure-on-request.html http://www.networksteve.com/enterprise/topic.php/SCCM_2012_-_Error_deploying_OS_image_from_task_sequence_media/?TopicId=66869&Posts=8 It's likely one of those will fix your issue. This appears to be the section where hte problem occours: <![LOG[401 - Authentication failure on request with anonymous access, retrying with context credentials.]LOG]!> <![LOG[using thread token for request]LOG]!> <![LOG[401 - Authentication failure on request with context credentials, retrying with supplied credentials.]LOG]!> <![LOG[Error. Status code 500 returned]LOG]!>

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigAdDomains You do lose some functionality if you have a functional level lower than 2003 mind. "If you configure discovery to filter and remove stale computer records, the Active Directory domain functional level must be a minimum of Windows Server 2003." Wouldn't have thought it would support anything older than 2000.

Have you sent both the x86 and x64 boot images to the DP (regardless of whether you use them both, you need them both there and distributed) Check the reference tab on the task sequence and go through each package that's referenced to ensure all of them are distributed. Finally if you haven't deployed them and you're only distributing them through a task sequence check the setting on each package or program which says something along the lines of "allow this package to be distributed through a task sequence without being deployed" both applications and packages have that option but both in different places and possibly worded slightly differently.

Sounds like you haven't distributed one of the packages referenced in your task sequence to the distribution point. Package BLV00001 - considering that package ID it's probably the boot image or your OS image.

It's ok, i've found the issue. I've got 5 applications in one application section of the sequence and i think one of those is wanting a restart but isn't initiating one, as soon as i remove that application from the task sequence everything goes fine. Interestingly though this is only an issue since the 2012R2 upgrade, worked fine this way previously. The application in question also appears quite early in the sequence so it must only bomb out once it hits another application that wants a reboot. Put it into it's own application sequence now to see if that resolves it. Thanks EDIT: that fixed it, huzzah!

Looks like the .net application was a bit of a red herring. I tried sticking a restart in before the dotnet install and it restarted itself part way through running perperation to run the restart task. Seems like it's either dropping out once a set amount of data is downloaded to the laptop or after a set amount of time, very strange.

I'm yet to try deploying to an existing machines (will test this soon) I've tried deleteing the packages completely and recreating and redistibuting them but that hasn't made any difference sadly, machine still instantly reboots itself once it gets to this point in the task sequence. Even though it's a given, this is the command my package runs: "dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT"

Hi There, I'm trying to deploy an image and as soon as it hits the .Net 4 package the imaging process instantly restarts the machine and loads windows, even if i have the F8 window open at the time. It gets to 80-90% on downloading the package at the point it restarts. Logs attached, but I'm unsure which logs i need as it leaves behind the _SMSTaskSequence folder in the root of C:, I've taken the smsts logs from both their and the Windows\CCM\Logs folders... This image installs the OS, drivers, office and a bunch of other apps fine up until the .net 4 or .net 4.5 tasks (both get the same error) ticking to continue on error has no effect, nor does having the F8 command window open. I should add the following two snippets of information: These worked fine before upgrading to 2012R2. I moved my sources share where the installers are held to a different drive not long after the upgrade to 2012 as i was running out of space, this meant redoing the share and security permissions on a new sources folder which i think i did correctly. Other applications and packages are installing fine from within the sources folder though. Thanks smsts from ccm logs.log smsts from smstasksequence.log smsts-20131031-155404.log smsts-20131031-230023.log

Is there of distinguishing different task sequence components to use different methods of installation? For example i'd prefer that the OS install went from DP first rather than download then for drivers to download and run locally as this seems to be quicker again on my setup, then again for the apps that run batch files to run locally rather than from the DP.

I've never used the "Access all content from DP" option before, I've always used download and run locally but i was testing it today and found the same thing, much quicker.....but would i be right in thinking that this change is the reason some of my packages that run batch scripts didn't work? Two of which execute .bat files with multiple lines. I assume that running them in a "remote run" scenario causes them to execute with a \\server\share based path for the executable rather than a local drive letter which is why they'd failed? .....I spent ages trying to work out why they kept getting an error and I've eventually come to that conclusion, can someone confirm if it sounds correct?

Hi there, I'm having some irritating issues since the upgrade to R2, I'm deploying a very basic image containing only a few applications. The OS Image deploys fine, the drivers deploy fine, the machine reboots to finalise the windows install and starts the boot image again to install the configmgr client. This runs through fine (or appears to) but as soon as the client install finishes I'm left with a blank screen (SCCM background wallpaper but no progress box). I have F8 support enabled in the boot image but i can't open up the F8 window while it's installing the client or while it's on the blank screen. The process proceeds to sit on the blank screen for aggggges (I've not timed it but it's well over 5 minutes) before eventually starting into windows, albeit without completeing the rest of the task sequence. I'll edit this post with the logs soon. Any ideas? EDIT: Well, i couldn't find the logs containing ANY errors whatsoever but i've managed to fix this.....it was either the setting "allow this program to be installed from the install package task sequence without being deployed" in the client install package, or it was becuase the "requirements" tab for my client manager package was ticked for "all windows 7 64bit" which i can't ever remember doing, but i assume that becuase the boot image belongs to windows 8.1 it wouldn't install the client with that ticked. Anyway, solved.

Exactly the same scenario as the OP here, esx 5.1U1 where my SCCM server is running, VMXNET3 NIC, SCCM2012R2 and downloading the image takes a very long time.

Would i be right in thinking that the backup/restore method requires you to install SCCM on the 2012R2 server as the same level of SCCM as you had backed up, before then upgrading SCCM to R2 as well after the restore? EDIT: Come to think of it, are there any guides around to doing this? I've never had to do a restore to an SCCM server before.

Multicast disabled: Imaging process works fine, I've done over 300 machines this way so far. I can always return to unicast and everything will work again after failing with mutlicast. Multicast enabled: Image bombs out with the 0x80091007 error at the very start, it says "creating a multicast session" then errors at the exact same moment it tries to start the applying operating system part. Unsure whether the multicast session even gets created though, because i never see any multicast routes appear on my router. (I'm not even sure if i should be able to, I assume though that something should show up in either "show ip mroute" or "show ip pim mroute" - this is a HP 8206zl) but at the same time the box behind switches to "Apply operating system" which leads me to believe it does. Here's the section from the log: <![LOG[Successfully completed the action (Partition Disk 0) with the exit win32 code 0]LOG]!><time="20:24:12.400-60" date="08-09-2013" component="TSManager" context="" type="1" thread="1620" file="instruction.cxx:3038"> <![LOG[MP server http://configmgr.Archway.local. Ports 80,443. CRL=false.]LOG]!><time="20:24:12.400-60" date="08-09-2013" component="TSManager" context="" type="1" thread="1620" file="utils.cpp:5300"> <![LOG[Setting authenticator]LOG]!><time="20:24:12.400-60" date="08-09-2013" component="TSManager" context="" type="1" thread="1620" file="utils.cpp:5322"> <![LOG[Set authenticator in transport]LOG]!><time="20:24:12.400-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="libsmsmessaging.cpp:7751"> <![LOG[Sending StatusMessage]LOG]!><time="20:24:12.422-60" date="08-09-2013" component="TSManager" context="" type="1" thread="1620" file="libsmsmessaging.cpp:4025"> <![LOG[Setting message signatures.]LOG]!><time="20:24:12.422-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="libsmsmessaging.cpp:1297"> <![LOG[Setting the authenticator.]LOG]!><time="20:24:12.422-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="libsmsmessaging.cpp:1327"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: configmgr.Archway.local:80 CCM_POST /ccm_system/request]LOG]!><time="20:24:12.422-60" date="08-09-2013" component="TSManager" context="" type="1" thread="1620" file="libsmsmessaging.cpp:8621"> <![LOG[Request was succesful.]LOG]!><time="20:24:12.442-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="libsmsmessaging.cpp:8956"> <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="20:24:12.442-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="executionenv.cxx:668"> <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="20:24:12.442-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="executionenv.cxx:668"> <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="20:24:12.442-60" date="08-09-2013" component="TSManager" context="" type="0" thread="1620" file="executionenv.cxx:782"> I've tried all the tricks of restarting services, restarting the server, updating the distribution point and validating everything involved. I'm using Server 2008R2 and my SCCM server is a vmware ESX5.1 VM, and i have SP1 installed. I've tried the suggestsions posted here: http://henkhoogendoorn.blogspot.co.uk/2013/02/multicast-error-0x80091007-during.html? and i've gone through my multicast setup with a fine toothcomb using the guide here: http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02610033/c02610033.pdf Here's the running configuration of my router just in case i have made any mistakes in the multicast setup that anyone can point out (this is the only router in the environment, SCCM server is on vlan 4, the machines I'm using to test multicast are on vlan 5) ; J9477A Configuration Editor; Created on release #K.15.04.0007 ; Ver #01:00:01 hostname "ProCurve Switch 8206zl" max-vlans 32 time daylight-time-rule Western-Europe module 1 type J8705A module 2 type J8705A trunk A21-A24 Trk1 Trunk trunk B21 Trk3 Trunk trunk B17,B19 Trk5 Trunk trunk B18,B20 Trk6 Trunk ip default-gateway 172.18.66.253 ip routing vlan 1 name "IP_BACKBONE" forbid A2 ip address 172.18.64.251 255.255.255.0 no untagged A1-A20,B1-B16,B22-B24,Trk1,Trk3,Trk5-Trk6 exit vlan 4 name "INFRASTRUCT" forbid A2 untagged A1,A12,A14,A17-A19,B1-B2,B5-B9,B13-B16 ip address 172.18.66.1 255.255.255.0 tagged B22,Trk1 ip igmp exit vlan 2 name "B_BLOCK" forbid A2 untagged B24 ip address 172.18.76.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 3 name "A_BLOCK" forbid A2 untagged A5-A10,A13,B10 ip address 172.18.68.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 5 name "ICT" forbid A2 untagged A11 ip address 172.18.65.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 6 name "iSCSI0" forbid A2 ip address 172.18.67.1 255.255.255.0 tagged Trk1 exit vlan 7 name "MEDIA_CENTRE" forbid A2 untagged Trk3 ip address 172.18.70.1 255.255.255.0 tagged A11,B1-B2,B8-B9,B13-B16 ip igmp exit vlan 8 name "VIDEO" forbid A2 untagged A20 ip address 172.18.79.1 255.255.255.0 tagged A5-A9,A11,B22-B24,Trk1,Trk3 ip igmp exit vlan 9 name "iSCSI2" forbid A2 untagged A15,Trk5 ip address 172.18.69.1 255.255.255.0 tagged Trk1 exit vlan 11 name "D_BLOCK" forbid A2 untagged B23 ip address 172.18.74.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 12 name "PRINT" forbid A2 ip address 172.18.71.1 255.255.255.0 tagged A5-A9,B13-B16,B22-B24,Trk1,Trk3 exit vlan 14 name "WIRELESS" forbid A2 untagged A4 ip address 172.18.77.1 255.255.255.0 tagged A5-A11,B1-B2,B8-B9,B13-B16,B22-B24,Trk1,Trk3 exit vlan 10 name "F_BLOCK" forbid A2 untagged B22 ip address 172.18.72.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 15 name "iSCSI1" forbid A2 ip address 172.18.78.1 255.255.255.0 tagged B13-B16 exit vlan 16 name "iSCSI3" forbid A2 untagged A16,Trk6 ip address 172.18.73.1 255.255.255.0 tagged B13-B16,Trk1 exit vlan 17 name "DOOR_SYSTEM" forbid A2 ip address 172.18.75.1 255.255.255.0 tagged A8-A9,A11,B1-B2,B8-B9,B13-B16,B22-B24,Trk1,Trk3 exit vlan 18 name "TBlock" forbid A2 untagged Trk1 ip address 172.18.80.1 255.255.255.0 tagged B1-B2,B8-B9,B13-B16 ip igmp exit vlan 20 name "DMZ" forbid A1,A3-A20,B3-B7,B10-B12,B22-B24,Trk3,Trk5-Trk6 untagged A2 tagged B1-B2,B8-B9,B13-B16,Trk1 no ip address exit vlan 21 name "vMotion" forbid A2 untagged B3-B4,B11-B12 ip address 172.18.84.1 255.255.255.0 exit vlan 22 name "GUEST_WIRELESS" forbid A2 untagged A3 tagged A4-A11,B1-B2,B8-B9,B13-B16,B22-B24,Trk1,Trk3 no ip address exit igmp-proxy-domain "WDS" 172.18.66.1 224.0.1.0 239.255.255.255 igmp-proxy-domain "Video" 172.18.79.1 239.192.79.10 239.192.79.10 power-over-ethernet pre-std-detect timesync sntp sntp unicast sntp server priority 1 172.18.66.25 ip route 10.7.116.0 255.255.252.0 172.18.66.12 ip route 192.168.11.2 255.255.255.255 172.18.66.253 ip route 195.137.89.208 255.255.255.252 172.18.66.253 ip route 213.18.249.18 255.255.255.255 172.18.66.12 ip route 213.129.90.244 255.255.255.255 172.18.66.12 ip multicast-routing router pim exit interface A21 flow-control exit interface A22 flow-control exit interface A23 flow-control exit interface A24 flow-control exit snmp-server community "public" unrestricted snmp-server host 172.18.66.16 community "public" snmp-server host 172.18.66.22 community "public" snmp-server host 172.18.75.3 community "public" snmp-server host 169.254.101.158 community "public" snmp-server host 172.18.66.26 community "public" snmp-server location "A Block Server Room" spanning-tree Trk1 priority 4 spanning-tree Trk3 priority 4 spanning-tree Trk5 priority 4 spanning-tree Trk6 priority 4 vlan 2 ip pim-dense ip-addr any exit exit vlan 3 ip pim-dense ip-addr any exit exit vlan 4 ip pim-dense ip-addr any exit igmp-proxy "WDS" exit vlan 5 ip pim-dense ip-addr any exit igmp-proxy "WDS" exit vlan 7 ip pim-dense ip-addr any exit exit vlan 10 ip pim-dense ip-addr any exit igmp-proxy "WDS" exit vlan 11 ip pim-dense ip-addr any exit exit vlan 18 ip pim-dense ip-addr any exit exit Thanks for any help on this, seems a lot of people are getting this problem and are unable to solve.