Jump to content

mattffrost

Member
  • Posts

    34
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by mattffrost

  1. Here is the solution <component name="Microsoft-Windows-DNS-Client" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <DNSServerSearchOrder> <IpAddress wcm:action="add" wcm:keyValue="1">192.168.0.1</IpAddress> </DNSServerSearchOrder> <Identifier>Local Area Connection</Identifier> <EnableAdapterDomainNameRegistration>false</EnableAdapterDomainNameRegistration> <DNSDomain>something.com</DNSDomain> <DisableDynamicUpdate>false</DisableDynamicUpdate> </Interface> </Interfaces> <UseDomainNameDevolution>true</UseDomainNameDevolution> <DNSDomain>something.com</DNSDomain> </component>
  2. Would anyone happen to know what DNS settings to put in the unattend.xml to get the following: Append Primary and connection specific DNS suffixes is selected Append parent suffixes of the primary DNS suffix is selected append these dns suffices (in order) is not selected (with no entries at all) DNS Suffix for this connection contains a value Register this connection's addresses in DNS is selected Use this connection's DNS suffix in DNS registration is not selected. Thank you.
  3. Ok, I got this to work the static IP, subnet mask and default gateway. The <identifier> by default is Local Area Connection but could be somthing else. The IPaddress value with /24 give a subnet mask of 255.255.255.0 /16 would give 255.255.0.0 the nexthopipaddress gives the default gateway. The prefix of 0.0.0.0/0 is something that finally got this to work. I was getting setup error before this. <settings pass="specialize"> <component name="Microsoft-Windows-TCPIP" language="neutral" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface> <Identifier>Local Area Connection</Identifier> <Ipv4Settings> <DhcpEnabled>false</DhcpEnabled> </Ipv4Settings> <UnicastIpAddresses> <IpAddress wcm:keyValue="1">192.168.0.1/24</IpAddress> </UnicastIpAddresses> <Routes> <Route wcm:action="add"> <Identifier>0</Identifier> <Prefix>0.0.0.0/0</Prefix> <NextHopAddress>192.168.0.254</NextHopAddress> <Metric>20</Metric> </Route> </Routes> </Interface> </Interfaces> </component> </settings>
  4. Well I learned out to set the subnet mask: Using the Windows System Image Manager I added the: x86_Microsoft_Windows_TCPIP to the unattended.xml answer file. For the value of IP address I added the subnet mask to the end 192.168.0.1/24 would give you 255.255.255.0 192.168.0.1/16 would give you 255.255.0.0 Now I am working on the gateway which I think is under routes--->NextHopAddress but when I add the route my vista setup fails I get a install windows error.
  5. I am currently using the BDD 2007 3.0.74.0 with Windows System Image Manager 6.0.5600.16384. I am using Windows System Image Manger to create an unattend.xml file that will be used for unattened vista installs. I am looking at the unattened help files and I am amazed that DefaultGatway and SubnetMask is now deprecated. We use static ip settings. Does anyone else have this same problem. What is really frustating is that you can add the x86_Microsoft-Windows-TCPIP_neutal setting to the Pass 4 specialize but it only gives a unicast IPaddress setting with no gatway and mask. I am just shocked at this.
  6. I tried the: http://www.remotesoft.com/linker/ I can get .net programs to work in Winpe 2.0 but my program does not work correctly. My program works correctly under Windows Vista but when I use the remotesoft it gives errors. I think this product is great for some .net programs but for others you may get unexpected results. I downloaded the trial version and the setup was very easy.
  7. Thanks for all the reply's. I have used the link http://colinfinck.de/en/peplugs/dotnetfx20pe/ for Windows XP winpe but this does not work for the new Windows Vista BDD 2007. I am also going to look at the: http://www.remotesoft.com/linker/ but it does not say it supports Windows Vista either. The BDD 2007 Winpe is available to everyone unlike the Winpe 2005 and 2004 that was only available to certain people. I hope it eventually catches on like BARTPE where things like getting the .net installed will happen. The new BDD 2007 currently comes with all the versions of Windows Vista bundled in. You just have to supply the correct product ID to install the one you want. What is so frustrating is that each install has a intall.wim. You can use a microsoft tool imagex.exe to open this install.wim and see how the framework is installed. The BDD 2007 WINPE uses a boot.wim which again you can use the imagex.exe to look at it. I have tried many times to take the files and registry setting from the intall.wim to the boot.wim. I think I am very close but I am missing just a few files. I think the think that makes me the most upset is the way I got the framework to work with winpe 2005 is not working with BDD 2007 Windows vista even though its the same 2.0 framwork. The Windows Vista uses some different files I take it. If anyone is interest in attainging bdd2007 let me know as I am a beta member testing it and if I find a solution to this I will post it.
  8. I am using BDD 2007 3.0.74 to deploy Windows Vista using Winpe. Does anyone know what files and registry settings to add to the boot.wim to get Microsoft .net Framwork to work with WINPE? I know the install.wim already has the framwork installed and I am trying to take those files and registry setting to add to the boot.wim. I think I am pretty close but can not quite get there. Any help would greatly be apreciated. Matt
  9. I would like to use MMC 3.0 to create a context menu extension snap for Active Directory Users and Computers. I have already sucessfully created a Property Sheet extension for Active Directory Users and Computes using MMC 3.0 with VB.Net. The problem I have is that under the MSDN MMC 3.0 there is only examples to extend namespace and property sheets and not context menu's. The examples are under http://msdn.microsoft.com/library/default....c0b11338caf.asp Click MMC Advanced Topics--->How to Create Extension Snap-ins Notice there is no context menu example. Any help would be greatly appreciated. Matt Frost
×
×
  • Create New...