RE: OSD Image Deployment via SMS advertisement (cannot connect to shar

Here's an addional error from my osdlaunch.log file created in the temp
folder of the current user that was logged on.

Successfully intialized Logging. OSDLaunch 12/11/2006 9:45:37 AM 3420 (0x0D5C)
Detected supported Advanced Client. OSDLaunch 12/11/2006 9:45:37 AM 3420
(0x0D5C)
SMS Client
GUIDGUID:C512A59D-330E-4B90-A0F8-B8C68B6AFEF9 OSDLaunch 12/11/2006 9:45:37
AM 3420 (0x0D5C)
Found Standard Client network access account OSDLaunch 12/11/2006 9:45:37
AM 3420 (0x0D5C)
Error getting image location and access account information. Code
0x80070490 OSDLaunch 12/11/2006 9:45:38 AM 3420 (0x0D5C)
OS Deployment advertisement failed to install OS Deployment agent!. Code
0x80070490 OSDLaunch 12/11/2006 9:45:38 AM 3420 (0x0D5C)
Saving Logs into the Temp Folder :
C:\DOCUME~1\tsnja\LOCALS~1\Temp\SMSOSD OSDLaunch 12/11/2006 9:45:38 AM 3420
(0x0D5C)


--
Nick Aquino
IT Professional
nick.aquino at Hotmail.com


"Nick" wrote:

Good Morning,
Here's my scenario:
Windows Server 2003 R2
Standard Edition
Service Pack 1
SMS 2003 2.50.4160.2000 Build 4160 (AD Scheme Extended, Advanced security)
OSD Feature Pack installed.

I am trying to deploy a test image that I built using the OS Image Capture
CD I created from the SMS Admin Console (Right-click image packages).

Once the wim file is copied to the server's network share that I manually
created, I open SMS admin console, right-click on image packages, and select
"new>operating system image package".

The new package is created. I modify the properties to include the network
drivers (same source as used for the image capture CD, same test computer, so
I know the drivers are good.)

After I add the network drivers, I then create an operating system program,
add the key code, and accept all the defaults.

I then create an advertisement targeting my test machine to deploy the
package to. I make it so that the user can run it independently.

The client (XP pro, sp2, firewall off/disabled, file sharing on, etc...)
receives the advertisement.

The client's execmgr.log file shows:

Policy deleted for advertisement FSS20018 package FSS0000D program GX280
IMAGE DEPLOY execmgr 12/11/2006 12:14:07 PM 3884 (0x0F2C)
Policy arrived for parent program Please Work execmgr 12/11/2006 12:14:07
PM 3020 (0x0BCC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
{
AdvertisementId = "FSS20019";
ClientID = "GUID:C512A59D-330E-4B90-A0F8-B8C68B6AFEF9";
DateTime = "20061211171407.736000+000";
MachineName = "DELETE-FDEB";
ProcessID = 1520;
SiteCode = "FSS";
ThreadID = 3020;
};
execmgr 12/11/2006 12:14:07 PM 3020 (0x0BCC)
Mandatory execution requested for program Please Work and advertisement
FSS20019 execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Creating mandatory request for advert FSS20019, program Please Work, package
FSS0000E execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Requesting content from CAS for package FSS0000E version
1 execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
{
AdvertisementId = "FSS20019";
ClientID = "GUID:C512A59D-330E-4B90-A0F8-B8C68B6AFEF9";
DateTime = "20061211171407.939000+000";
MachineName = "DELETE-FDEB";
PackageName = "FSS0000E";
PackageVersion = "1";
ProcessID = 1520;
ProgramName = "Please Work";
SiteCode = "FSS";
ThreadID = 1344;
};
execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Successfully raised SoftDistWaitingContentEvent event for program Please
Work execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Execution Request for program Please Work state change from NotExist to
WaitingContent execmgr 12/11/2006 12:14:07 PM 1344 (0x0540)
Content is available for program Please Work. execmgr 12/11/2006 12:14:08
PM 3336 (0x0D08)
Notify user mandatory program Please Work is about to run execmgr 12/11/2006
12:14:08 PM 3336 (0x0D08)
Execution Request for program Please Work state change from WaitingContent
to NotifyExecution execmgr 12/11/2006 12:14:08 PM 3336 (0x0D08)
Executing program osdlaunch.exe in Admin context execmgr 12/11/2006 12:14:10
PM 3884 (0x0F2C)
Execution Request for program Please Work state change from Running to
Running execmgr 12/11/2006 12:14:10 PM 3884 (0x0F2C)
Invalid username, missing domain name execmgr 12/11/2006 12:14:10 PM 3884
(0x0F2C)
Checking content location \\HQSMS01\SMSPKGE$\FSS0000E\ for
use execmgr 12/11/2006 12:14:10 PM 3884 (0x0F2C)
Successfully selected content location
\\HQSMS01\SMSPKGE$\FSS0000E execmgr 12/11/2006 12:14:10 PM 3884 (0x0F2C)
Executing program as a script execmgr 12/11/2006 12:14:10 PM 3884 (0x0F2C)
Successfully prepared command line
"\\HQSMS01\SMSPKGE$\FSS0000E\OSDLaunch.exe" execmgr 12/11/2006 12:14:10
PM 3884 (0x0F2C)
Command line = "\\HQSMS01\SMSPKGE$\FSS0000E\OSDLaunch.exe", Working
Directory = \\HQSMS01\SMSPKGE$\FSS0000E\ execmgr 12/11/2006 12:14:10 PM 3884
(0x0F2C)
Created Process for the passed command line execmgr 12/11/2006 12:14:11
PM 3884 (0x0F2C)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "FSS20019";
ClientID = "GUID:C512A59D-330E-4B90-A0F8-B8C68B6AFEF9";
CommandLine = "\"\\\\HQSMS01\\SMSPKGE$\\FSS0000E\\OSDLaunch.exe\"";
DateTime = "20061211171411.220000+000";
MachineName = "DELETE-FDEB";
PackageName = "FSS0000E";
ProcessID = 1520;
ProgramName = "Please Work";
SiteCode = "FSS";
ThreadID = 3884;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "\\\\HQSMS01\\SMSPKGE$\\FSS0000E\\";
};
execmgr 12/11/2006 12:14:11 PM 3884 (0x0F2C)
Raised Program Started Event for Ad:FSS20019, Package:FSS0000E, Program:
Please Work execmgr 12/11/2006 12:14:11 PM 3884 (0x0F2C)
Program exit code 0 execmgr 12/11/2006 12:14:12 PM 3336 (0x0D08)
Looking for MIF file to get program status execmgr 12/11/2006 12:14:12
PM 3336 (0x0D08)
Script for Package:FSS0000E, Program: Please Work succeeded with exit code
0 execmgr 12/11/2006 12:14:12 PM 3336 (0x0D08)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramCompletedSuccessfullyEvent
{
AdvertisementId = "FSS20019";
ClientID = "GUID:C512A59D-330E-4B90-A0F8-B8C68B6AFEF9";
DateTime = "20061211171412.064000+000";
MachineName = "DELETE-FDEB";
PackageName = "FSS0000E";
ProcessID = 1520;
ProgramName = "Please Work";
SiteCode = "FSS";
ThreadID = 3336;
UserContext = "NT AUTHORITY\\SYSTEM";
};
execmgr 12/11/2006 12:14:12 PM 3336 (0x0D08)
Raised Program Success Event for Ad:FSS20019, Package:FSS0000E, Program:
Please Work execmgr 12/11/2006 12:14:12 PM 3336 (0x0D08)
Execution is complete for program Please Work. The exit code is 0, the
execution status is Success execmgr 12/11/2006 12:14:12 PM 2136 (0x0858)

After that log, I check in the event viewer and see under the system log
that the osdagent_service was sent a start control, started, stops, and then
gives me "The OSDAgent_Service service terminated with the following error:
A specified logon session does not exist. It may already have been
terminated.

I have been receiving this scenario if I have a generic account set up in
Advanced Client Network Access account, if I have a domain admin's account
listed, if I have no account listed.

I wanted to test to see if the client even attempts to run the app, so I
renamed osdlaunch.exe to osdlaunch.exe.old. Sure enough, I received an error
that the file was not found. So, I know the package is being contacted, but
its' failing. I'm getting a status code of 0 returned because to the
distribution point showing the success of the passing of the command line.

In the SMS admin console's status message viewer for the advertisement, it
goes like this:

User created and advertisement...

SMS Offer manager successfully processed advertisement...

Advertisement was received...

the program for advertisement "fs20019" has not yet started because the
content for the package has not been acquired.

Program started for advertisement "FSS20019" ("FSS0000E" - "Please Work").
Command line: "\\HQSMS01\SMSPKGE$\FSS0000E\OSDLaunch.exe"
Working directory: \\HQSMS01\SMSPKGE$\FSS0000E\
User context: NT AUTHORITY\SYSTEM

The program for advertisement "FSS20019" completed successfully ("FSS0000E"
- "Please Work").

AND THEN THIS:

The OS installation failed to connect to the distribution point
\\HQSMS01\SMSPKGE$\FSS0000E.

Like I said before, I have tried domain admin account in the advanced client
network access account and it still doesn't work. It appears to contact the
share and access it when i rename files. Someone help... Please?!!???

--
Nick Aquino
IT Professional
nick.aquino at Hotmail.com
.

Relevant Pages

  • OSD Image Deployment via SMS advertisement (cannot connect to shar
    ... The new package is created. ... I then create an advertisement targeting my test machine to deploy the ... Raising event: ... Advanced Client Network Access account, if I have a domain admin's account ...
    (microsoft.public.sms.swdist)
  • Re: how long time SMS take to deploy program of a package, Run program Silent Mode
    ... Running setup directly from Distribution Point ... It take a long time to deploy SMS on selective collection, ... If I delete the advertisement, how long time it will take to remove ... I advertise a program of Package "A", ...
    (microsoft.public.sms.installer)
  • RE: OSD Image Deployment via SMS advertisement (cannot connect to
    ... One log tells you the account that is being used ... test machine and push the package again. ... OS Deployment advertisement failed to install OS Deployment agent!. ... Raising event: ...
    (microsoft.public.sms.swdist)
  • Re: BITS and SMS
    ... you can set the advertisement for a specific ... BITS should download the package from the DP to the clinet ... I've set the advertisement to download the package for the ... Kim Oppalfens - Sms Expert for lack of any other expertise ...
    (microsoft.public.sms.swdist)
  • Re: How does an SMS client know whether it should run a particular pck
    ... trickiest aspects of SMS that I know of (and I know a lot of tricky SMS ... the package and program must be ... If the advertisement varies but the package ... >> If an SMS Client receives a new mandatory advertisement for a package it ...
    (microsoft.public.sms.swdist)