OSD Image cannot find Distribution Point

[Mungoblack]

I am running SMS 2003 SP1. I have created an image on a desktop PC which i
have then successfully captured using the capture wizard. In the admin
console i have then created a package and a program. I have updated the
distribution point ok and set all the relevant properties on the program
tabs. I have then created the boot disk with my additional nic drivers. The
sms wizard starts ok and boots into the screen where it shows which packages
are on my distribution point. If i click next i then get the following
message -

"There are no distribution points currently available for the operating
system package. Please select another operating system package or contact
your administrator for assistance"

If i click to select from another location i can then browse and install my
image ok. I have updated the DP again but i still cant seem to install my
image from the distribution point?

Any ideas????

Thanks

[borje]

Hi!

I had the similar problem and it was because I had forgot to enable Webdav
(IIS config) on my Primary site server.

/Borje

Borje Carlsson
LAN Assistans AB
Sweden

"Mungoblack" <mungo...@ntlworld.com> wrote in message
news:r5fFd.139$CM...@newsfe1-gui.ntli.net...

[Dave Halperin]

This is a known bug. You should ahve a folder called "HOTFIX" where you
unpacked the OSD, if not go to
http://support.microsoft.com/default.aspx/kb/888311

This will give you the hotfix.

"borje" <borje.c...@lanassistans.se> wrote in message
news:eRVROqP%23EHA...@tk2msftngp13.phx.gbl...

[Mungoblack]

Thanks for that, i have now changed the webdav setting although i still
cannot connect to the DP.

"borje" <borje.c...@lanassistans.se> wrote in message
news:eRVROqP%23EHA...@tk2msftngp13.phx.gbl...

[Dmitry Mashkov]

Great! Thank you for the info, we had this problem and Microsoft Gold
Partner was not able to solve it...

"Dave Halperin" <Dave_H...@bose.com> сообщил/сообщила в новостях
следующее: news:eNZ2U5X%23EHA...@TK2MSFTNGP11.phx.gbl...

[Mungoblack]

I have installed the hotfix and intersetingly it did not overwrite the dll
with the new version??? I therefore extracted the dll and installed it
manually and did a regsvr32 which succeeded. I then reinstalled the hotfix
so as to restart all required services and checked the dll was the correct
version. I then advertised the new operating system to a PC which i wanted
to rebuild. The PC recieved the advertisement and ran the package ok. When
it came to the automatic reboot i got the following error -

"The operating system installation failed. Could not connect to the
installation package on \\servername\smspkgf$\mrl0000A The network location
cannot be reached. See windows help (8000704CF)"

"Mungoblack" <mu...@nospam.com> wrote in message
news:LMAFd.406$3g5...@newsfe5-win.ntli.net...

[Brett Flegg (MS)]

Hi,

Just to give you some context, here is what happens when you boot from an
Image Installation CD:
1. Startup Windows PE and load network drivers
2. Contact the MP and request available distribution points
3. Connect to the distribution point using the Advanced Client Network
Access Account and install the OS

It looks like you got through steps 1 and 2 okay, but failed to connect to
the distribution point. The most common cause of this is an out-of-date or
invalid Advanced Client Network Access Account. Please verify that the
account is set as follows: The Advanced Client Network Access Account can be
configured in the 'General' tab of the 'Software Distribution' dialog box
using the SMS Admin console under 'Systems Management Server-->Site
Database-->[Your Site Code]-->Site Settings-->Component Configuration' and
has access to the given share. If you change this account, you have to
re-create the image installation CD. If you are still having problems,
please use the lab shell and try to manually connect to the given share
using the given credentials .

Please let us know how things work out,

-- Brett

--

brett flegg | software design engineer/test | SMS | OSD FP

This posting is provided AS IS with no warranties and confers no rights.

"Mungoblack" <mu...@nospam.com> wrote in message

news:52WFd.507$1B6...@newsfe1-gui.ntli.net...

[Mungoblack]

Thanks Brett. I will check the access accounts. Can you tell me how to
use/create the lab shell?
Thanks

"Brett Flegg (MS)" <bfl...@online.microsoft.com> wrote in message
news:eQsgNFo%23EHA...@tk2msftngp13.phx.gbl...

[Brett Flegg (MS)]

Hi,

A full set of instructions are included in the 'Using the Lab Shell for
Windows PE' section of the OS Deployment FP Users Guide, here is an exert:

The shell enables you to access a command shell in the Windows PE
environment so that you can view the state of the computer and run your
scripts to determine reasons for failure. To use the lab shell:

1. Backup OSDSHELL.EXE by renaming it or copying it to a safe location
2. Rename OSDSHELL.LAB.EXE to OSDSHELL.EXE
3. In the SMS Administrator console, right-click the OS Deployment package
you are testing with and select Update OS Package Files from the All Tasks
menu.
4. If you are testing with an OS Image Installation CD, you must create a
new CD by right-clicking on the Image Packages item and selecting Create OS
Image Installation CD from the All Tasks menu.

When the destination computer boots into Windows PE - either from the hard
drive or a CD - you can open a command shell by pressing F8 while the shell
is initializing.

-- Brett
--

brett flegg | software design engineer/test | SMS | OSD FP

This posting is provided AS IS with no warranties and confers no rights.

"Mungoblack" <mu...@nospam.com> wrote in message

news:sU4Gd.161$Qg5...@newsfe6-gui.ntli.net...

[Mungoblack]

Hi Brett thanks for your help. Ive got it working now. I got into the lab
shell command prompt and it wasnt picking up an IP address as the NIC
drivers wernt being installed. Ive now set the package to include additional
NICs and it works fine now if i deploy it as an advertised package. I will
try it using the CD boot method and see it that works aswell..

Thanks

"Brett Flegg (MS)" <bfl...@online.microsoft.com> wrote in message

news:%23O$DBnK$EHA....@TK2MSFTNGP12.phx.gbl...

[Brett Flegg (MS)]

Hi,

Great! Please note that you will need to add custom network drivers to the
Image Installation CD as well (there will be a screen in the Wizard that
prompts you for this).

Here is a list of places you need to add custom network drivers to:

1. The Image Capture CD - You will need to add custom network drivers to the
image capture CD when you create it. This will only add the drivers to the
CD -- not to images created with the CD (see #2)

2. Image Packages - You will need to add custom network drivers to image
packages that you will deploy with an Advertisement. You can do this in the
package properties dialog box. This will add the drivers to the packages
that are on the site server -- not to image installation CDs that you create
in the future (see #3)

3. Image Installation CD - You will need to add custom network drivers to
any image installation CD when you create it.

I know this is a lot of places to put custom network drivers -- I often
forget to add them myself. A common way around this is to create a custom
WinPE that has the drivers you need already built in. Please see the
'Customizing the Windows Pre-installation Environment' section in the OSD FP
Guide for more information on this.

-- Brett

--

brett flegg | software design engineer | SMS | OSD FP

This posting is provided AS IS with no warranties and confers no rights.

"Mungoblack" <mu...@nospam.com> wrote in message

news:eiUGd.239$751...@newsfe1-win.ntli.net...