Getting Error: Task sequence launcher advertisement failed!. Code 0x80070003
Hello,
I have followed the instructions in Quick Start Guide for Microsoft System Center Configuration Manager 2007 exactly as instructed. When i advertise the Target task sequence to an existing client i get teh following errors in smsts.log.
Error executing StartService(). Code 0x80070003
Task sequence launcher advertisement failed!. Code 0x80070003
File "C:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002)
When i run the advertisement from the client it does not create the _SMSTaskSequence folder so therefore it cannot start the service. The ConfigMgr client is healthy and there are no errors in ccmsetup.log.
Anyone know why this would happen?
thanks
Answers
The problem is with the AD sites. Configure an IP-subnet boundary and see if that works out for you too.
Also Discovery does not really work well with Site boundaries!
All Replies
Do you have the boot images on your distribution points?
Hello,
Yes, i have distributed my WinPE_Custom boot image to all distribution points.
thanks
So just as a test, i booted to the SCCM Boot CD on a PC that i added to the database manually and i get "Unable to determine the ConfigMgr site for this client". I click next and i get the form which allows me to add the system manually to the ConfigMgr site database. If i add it manually, then the build starts and completes without any issues.
If i check BDD.log this is what i get:
>FindFile: The file CustomSettings.ini could not be found in any standard locations.
>Unable to find CustomSettings.ini, rc = 1
>Property AssignedSite is now =
>Unable to determine assigned site using any available IP addresses
>Error executing web service http://SCCMServer/MicrosoftDeployment/UnknownComputer.asmx/IsComputerKnown: >The server name or address could not be resolved
(-2147012889)>Unable to call IsComputerKnown web service.
As i mentioned, i have followed the instructions from top to bottom for a third time and i get the same issue. The ConfigMgr site works perfectly as i am able to do all normal operations aside from OSD.
The CustomSetttings_Target package has been distributed but i did not edit CustomSettings.ini because i'm using Task Sequences to configure settings such as Network and software and the deployment is in one location with a single AD OU, Gateway, etc...Do i need to edit CustomSettings.ini as i did for SMS 2003 OSD where i configured Gateway, OU, etc...?
The MDT 2008 Files package is created and distributed. The only thing is that my MDT 2008 installation does not have any OS files and Applications as i'm only doing deployments with SCCM. I did run the SCCM integration before i started the process. i'm assuming that only needs the scripts directory?
Anyone from the Deployment team have any ideas?
Do you have SP1 and/or R2 installed? Did you extend your AD schema? Have you correctly defined your site boundaries? Is the system you're trying to build an image on located on the correct subnet for that AD site you've defined?
nick
Hello,
Thanks for the reply as this is extremely frustrating.
Server = 2003 R2 SP2
Active Directory has been extended with no errors
Boundaries are based on AD Sites and the subnet for this particular client is configured in AD Sites and Services. I do not have IP Subnet boundaries, only AD Sites.
Thing to note is that this SCCM infrastructure was an upgrade to an existing SMS 2003 site. The only thing that changed was that Boundaries were originally IP Subnets but when we upgraded to SCCM, we changed them to AD Sites.
Thing to note is that i can boot to the SCCM Boot CD and manually run the Task Sequence so it does infact know where to get the package from.
The problem is with the AD sites. Configure an IP-subnet boundary and see if that works out for you too.
Also Discovery does not really work well with Site boundaries!
Hmmm.....It is hard for me to trust in place upgrades. Even though MS may claim it is a smooth process.
This may be a redundant question, but is the IP subnet correctly defined in your AD site? Also, when I asked if you had SP1 or R2 installed, I meant that for SCCM as opposed to Windows Server. So do you have SP1 or R2 installed?
I changed the AD site boundary to an IP Subnet boundary and it worked!!!
It is very strange that AD Site boundaries does not work well. We have many IP Subnets and would be a big pain to maintain this list in SCCM...
thanks for you help
- Wally indicates in past comment that SCCM boundaries are NOT necessary and you can "get along without them" If this is so, why would including the subnet boundary make a difference? I cannot get advertisements to run unless my clients are in a boundary. So my question. Are boundaries necessary or not? and why or why not?
This information is just pulled from the product documentation, under topic "Choose Configuration Manager Boundaries". It seems to answer your question.
Computers are assigned as clients to Configuration Manager 2007 sites according to the boundaries you configure in the Configuration Manager console. Boundaries are defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.
When creating Configuration Manager 2007 boundaries, you must specify the type of network connection that the boundary will operate on. You must also decide if the boundary will be used for either a Slow or unreliable or Fast (LAN) network connection.
Configuration Manager 2007 clients have the ability to roam. Roaming is the ability to move a computer that is running the Configuration Manager 2007 Client, from the designated boundaries of a Configuration Manager 2007 site to within the assigned boundaries of another Configuration Manager 2007 site or another network location not defined as a Configuration Manager boundary for any site at all. Ensure that you plan for client communications and manageability when clients roam from one Configuration Manager 2007 site to another. For more information about Configuration Manager 2007 client roaming, see About Client Roaming in Configuration Manager.
Furthermore, in the About Client Roaming section
Roaming in Configuration Manager 2007 refers to the ability of clients to move between sites in the Configuration Manager hierarchy and continue to be managed while making the best use of network resources
...
When a roaming client needs to access content such as an advertised program's package source files, it sends a content location request to the resident management point if it has global roaming capability, or to its default management point if it has regional roaming capability.
So I would conclude that, yes, adding the boundaries do make a difference. The behavior your are getting with your clients is what I would expect. Hope this was of any help!
nick
