Re: OSD dosnt work with CISCO DHCP and VLANs
- From: "Sonnichsen" <Sonnichsen@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Jan 2006 23:26:02 -0800
Thanks a lot for the very quick response, I will try both solutions.
However, do you know want is the actual problem?
Is it the CISCO box and in that case what is missing/wrong or is it WinPE?
It is probably not the PXE part as it is possible to F12 install using a
normal RIS installation, but if I choose my OSD image during F12 installation
I do get WinPE started but it doesnt get any further.
--
Soren Holst Sonnichsen
TopNordic A/S
Denmark
"Johan Arwidmark" wrote:
> Try change the bootfile option to OSChooser\i386\startrom.com and
> remove option 60 ascii "PXEClient"
>
> Also make sure that the IP range is listed as a subnet in your Active
> Directory Site (or RIS will limit the number of concurrent
> connections)
>
> You can also create a boot-in-ram version of the OSD Installation CD
> and PXE boot it from any PXE server.
>
> To create a boot-in-ram version:
>
> 1. Update OSD with Windows PE 2005 built from Win2003 SP1 media
> 2. Copy the Winpe folder from a Windows Pe 2005 cd to c:\
> 3. Create a folder named c:\work
> 4. Create a new OSD Installation CD iso file and copy to c:\work
> 5. Create a text file named Winnt.sif in the workdir folder
>
> [SetupData]
> BootDevice = "ramdisk(0)"
> BootPath = "\i386\System32\"
> OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd
> /rdpath=\OSD_INSTALL_CD.ISO"
>
> Note: the line beginning with OsLoadOptions may have been wrapped by
> the news reader.
>
> 6. Create a folder named c:\work\i386
>
> 7. Copy the following files from the Windows PE 2005 CD to
> c:\work\i386
>
> \i386\bootfix.bin
> \i386\ntdetect.com
> \i386\Setupldr.bin
>
> Create a new bootable iso by starting a command prompt and type the
> followinbg command.
>
> cd /d C:\winpe
>
> oscdimg -h -n -betfsboot.com C:\work C:\osd_install_inram.iso
>
>
> Note: Will require 256 MB ram of the computers (you also may want to
> reduced the size of Winpe).
>
> regards
>
> Johan Arwidmark
> Microsoft MVP - Setup/Deployment
>
>
> On Tue, 17 Jan 2006 07:22:03 -0800, "Sonnichsen"
> <Sonnichsen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >I have deployed SMS 2003 SP1 and have installed OSD FP. My network consists
> >of several VLANs and a CISCO DHCP server. I can deploy OSs succesfully all
> >over the organisation in all VLANs using SMS advertisements or installation
> >CDs. I have a RIS server which can be used to install OSs in all VLANS.
> >However when I try to use the RIS server to deploy images from SMS it fails.
> >When I initiate the F12 OSD installation WinPe starts up and then stops for
> >ever. After a lot of examination I found out that the WinPE client gets an IP
> >adress, a subnet mask and a gateway but absolutely nothing else, no DNS, no
> >WINS. It cant even ping the gateway (using the labshell) so it probably dont
> >even get a proper TCP stack. And now the strange thing comes, when I replace
> >the CISCO DHCP with a Microsoft 2003 DHCP server everything works like a
> >charm through VLANs and all. My problem is that I have to use the CISCO DHCP.
> >What is missing from the CISCO DHCP? Please help!!
>
>
.
- Follow-Ups:
- Re: OSD dosnt work with CISCO DHCP and VLANs
- From: Johan Arwidmark
- Re: OSD dosnt work with CISCO DHCP and VLANs
- References:
- Re: OSD dosnt work with CISCO DHCP and VLANs
- From: Johan Arwidmark
- Re: OSD dosnt work with CISCO DHCP and VLANs
- Prev by Date: RE: OSD Image Installation fails - Can't find DP
- Next by Date: OSD loadstate fails Error 1008 reported by USMT
- Previous by thread: Re: OSD dosnt work with CISCO DHCP and VLANs
- Next by thread: Re: OSD dosnt work with CISCO DHCP and VLANs
- Index(es):
Relevant Pages
|
