Jazkal

what do you mean by scratchspace? I know that a base wim (150 mb) takes around 385 mb of ram to boot correctly. So a 300 mb wim would need 800 mb or so. If the scratchspace limits that to 512mb, that would be the problem.

your password has to be in hex. Use the vncconfig.exe to set a password, then grab the hex from the registry.

That was my problem. thanks guys.

Yes, I have a valid IP for WinPE via DHCP. using this command line: vncviewer.exe 127.0.0.1::5000 works But I can still not access it remotely. Firewall is off, what else could be blocking it?

I have all the files for VNC copied to X:\Windows\System32\ winvnc4.exe wm_hooks.dll logmessages.dll I then run: wpeinit.exe DisableFirewall Then I run: winvnc4.exe PortNumber=5900 Password=xxxxxxxxxxxxxxx It runs in User-Mode and waits. But all attemts to connect to the box fails.

Did you get it working? If so, can you give us a step by step?

http://tinyurl.com/y9wwrsj

what you are looking for is called 'slipstream'.

I wish they would at least offer a .Net Framework. That would open up a lot of development.

1) WinPE is a static environment (for the most part). You make your changes and mods to WinPE, before you boot it up, not after. 2) WinPE doesn't include IE. 3) WinPE doesn't support MSI installations (see #1).

So instead of loading drivers based on Ven and Dev numbers, these broadcoms are loading off this: b06bdrv\l2nd&pci_164c14e4

I pulled those from WinPE using: devcon find pci* I'll try the dos scan on monday. thanks.

So I'm building WinPE from the newest WAIK. Has to be x64 version, because it has to install Windows 2008 R2 via network (which is x64 only, no x86 version to call setup.exe with). I have a number of boxes that I can not get the Nics to grab a DHCP IP at all. Dell Poweredge R710 Nics: PCI\VEN_14E4&DEV_1639&SUBSYS_02351028&REV_20\FEAB2B0100 : Broadcom BCM5709C NetXtreme II Monolithic Driver PCI\VEN_14E4&DEV_1639&SUBSYS_02351028&REV_20\FEAB2B0301 : Broadcom BCM5709C NetXtreme II Monolithic Driver #2 Dell Poweredge R900 Nics: PCI\VEN_14E4&DEV_164C&SUBSYS_01F01028&REV_12\7&36AE1548&0&0000180018: Broadcom BCM5708C NetXtreme II GigE PCI\VEN_14E4&DEV_164C&SUBSYS_01F01028&REV_12\7&3D48B3B&0&0000280018: Broadcom BCM5708C NetXtreme II GigE #2 PCI\VEN_14E4&DEV_164C&SUBSYS_01F01028&REV_12\7&57BC5F4&0&0000100018: Broadcom BCM5708C NetXtreme II GigE #3 PCI\VEN_14E4&DEV_164C&SUBSYS_01F01028&REV_12\7&F552F72&0&0000200018: Broadcom BCM5708C NetXtreme II GigE #4 HP DL585 G2 Nics: PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&0880: Broadcom BCM5706C NetXtreme II GigE PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&1080: Broadcom BCM5706C NetXtreme II GigE #2 Tyan S3992 Nics: PCI\VEN_14E4&DEV_166A&SUBSYS_166A14E4&REV_10\4&2DC1BBBE&0&2038: Broadcom NetXtreme Gigabit Ethernet PCI\VEN_14E4&DEV_166A&SUBSYS_166A14E4&REV_10\4&2DC1BBBE&0&2138: Broadcom NetXtreme Gigabit Ethernet #2 I have tried all the latest drivers from Broadcom, HP, and Dell. But the part that really makes me think, is that these: Dell Poweredge 2950 Mk II Nics: PCI\VEN_14E4&DEV_164C&SUBSYS_01B21028&REV_11\5&2EADD4B0&0&0000E0: Broadcom BCM5708C NetXtreme II GigE PCI\VEN_14E4&DEV_164C&SUBSYS_01B21028&REV_11\7&1DF4CEC7&0&0000000010: Broadcom BCM5708C NetXtreme II GigE Dell Poweredge 2950 Mk III Nics: PCI\VEN_14E4&DEV_164C&SUBSYS_01B21028&REV_12\5&43097C6&0&0000E0: Broadcom BCM5708C NetXtreme II GigE PCI\VEN_14E4&DEV_164C&SUBSYS_01B21028&REV_12\7&2A8A8A3B&0&0000000010: Broadcom BCM5708C NetXtreme II GigE #2 These Broadcoms work fine. Which have the same Ven and Dev ID's as the R900 Nics. Anyone have any ideas?

http://www.microsoft.com/downloads/details...39c26d3b3b34#tm Was released on 8/6/2009

So, from my reading, this is what I'm seeing: Just to let everyone know, The server side has Transaction Server installed, but not WDS. The namespaces are setup on the server using the command line tool 'WDSUTIL.EXE' Connections to the server from the client (WinPE2.x +) are with the command line tool 'WDSMCAST.EXE' Does anyone have any actual real world command line examples on this? (I see how to pull down individual files, but what about unloading the contents of a WIM to the root of C? Or do I have to multicast the WIM to the C drive then extract the OS files?)

Yeah, I love how hard they make finding info on TechNet. Trying to figure out if I gain anything by using R2 or not.

I found some docs, will post more once I run some tests: http://technet.microsoft.com/en-us/library...964(WS.10).aspx http://technet.microsoft.com/en-us/library...475(WS.10).aspx

Thanks for the tip, i'll keep the thread updated if I find anything.

Can you describe from a high level how you are using multicast from Win2k8? Thanks

Do you know what service, or application in Windows 2008 handles the multicast functions?

I'm looking for info/details on using Multicast on WinPE3.x with a Win2k8 backend server. Not looking for WDS, looking to create my own solution using the bare bones tools. Anyone actually have first hand info on it? Here are some old blog postings: Multicast Deployments with Windows Server 2008 Revisiting Windows Deployment Services

Microsoft will not be supporting R2 deployed from x86 PE.

I had the same issue. For me it was actually a number of issues, depending on the hardware. On some systems, I had to include the video drivers in the winpe21 build process. On others, it was 16 instead of 32. ie: 1024x768x16 vs 1024x768x32 And I went with an autoit script to do the res changes, because setres wouldn't work for me in winpe2.x

I just added them to my user or system paths.

looks like your unmount was not successful.