Jump to content

JononE

Member
  • Posts

    16
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United Kingdom

About JononE

JononE's Achievements

0

Reputation

  1. Solved It was a varation of what I posted before... The NEC M5410 was a "acpipc_up" instead of an "acpiapic_up" so I used the sysprep.inf file to convert the HAL type. Done n Dusted. If anyone gets this fault I think the easiest way to determine a computers HAL processor type is... If a computer can’t see an XP image – sysprep – capture it – look at the properties. Use an existing image – modify the sysprep.inf file – sysprep it twice – capture image.
  2. Been doing a lot of research on this and if anyone's interested... here are my findings. When you network boot your computer and the boot loader starts to load, it does perform a HAL check on the computer you are deploying the image to. This is only really an issue if your deploying XP as Vistas HAL check is a lot better. The problem of images not appearing is to do with the processor type of the computer used to create the image... http://forums.microsoft.com/TechNet/ShowPo...2&SiteID=17 So if it's a uni processor (UP) or a multi processor (MP) (You can find that out by right clicking on the image on the WDS Server and looking at the properties) the image XP can only be deployed to computers wit hthe same processor spec. You can convert an image from UP to MP or vice versa by editing the sysprep.inf file and adding... *ADD IF WANTING TO MAKE UNIPROCESSOR BECOME MULTIPROCESSOR UpdateHAL = ACPIAPIC_MP,%WINDIR%\inf\hal.inf *ADD IF WANTING TO MAKE MULTIPROCESSOR IMAGE BECOME UNIPROCESSOR UpdateUPHAL = ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf You then need to sysprep the PC with a mini setup. The mini setup part is what changes the processor type so before you capture this image, you need to sysprep it again or it doesn't work. When the image has been captured, check the processor type and it should have been changed. This though has not solved my problem. I have e-mailed Microsoft via Technet and I am currently awaiting an answer. http://forums.microsoft.com/technet/ShowPo...;postid=3146084
  3. Hello I wonder if anyone has had this same problem, and hopefully solved it! I created an image using XP and syspreped the image, then captured it using WAIK and stored it on the WDS Server. I then can deploy that image over the network (pressing F12 and booting into the nice GUI) without a problem.... but if I boot up with a slightly different spec Computer (we are talking about a NEC 5210 and NEC 5410 almost identical spec machines) all the images are shown on the WDS Server except the 5210 image I created. Does WDS do a quick spec of the PC it's deploying it to ? The machine that doesent see the image I want to deploy sees all the other images, and will install any other image - except the one I want to deploy (typical!) I'm trying to make a generic Laptop image for all the Laptops in the company - got 3 out of 5 working but the NEC 5410 and an Acer Laptops just don't see the Laptop image I freshly created and want to deploy even though a Samsung, Toshiba and 5210 all see and install that image. I can't see it being drivers in the boot.wim (which was my first idea) because the dissapearing image works on other Laptops - just not on all of them... and I don't think it's a chipset issue because the 5210 and 5410 are almost identical. Has anyone else seen this ? resolved this ? any ideas ? another Microsoft problem driving me mad LOL Thanks!
  4. I was under the impression that adding a valid product key was usless anyway ? as Vista looks for a key Server to licence itself against. I thought you had to contact Microsoft with your Product Key to get the details and user information for your Key Server, and Vista then uses that... Or am I totally lost on this ?
  5. Hello! I have searched for an answer to this, but I don't know the correct term to ues so finding it in the forum is increasingly difficult. I have some CAB and MSP updates that I wish to deploy with my image via WDS but how to I put the updates into the image ? I'm guessing I use SIM as I have found the bit that says insert a CAB file (In packages) but how do I insert a MSP file ? Also am I right in thinking to deploy new drivers you just create folders in the Distribution share in the $OEM$ folder called 000_chipset for example, and bung the SIF files in there ? I haven't tested it yet but thats what I'm reading currently. Cheers for the reply!
  6. That was ripped straight out of my working XML file, try it first just to see what happens.
  7. Here you go! Just add this too your XML file, hopefully this should work. The Fist partition is called 'System' and is 20Gb, the second partition is extended to the rest of the drive and is called 'Data', so you can modify the name if you wish. As for Vista's main system drive has to be at least half the overall size of the drive ? I don't think so. I setup the partion so the C: drive is 35Gb and the second partition fills the rest of the drive, and we use a 160Gb drive without a problem. <DiskConfiguration> <Disk wcm:action="add"> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>System</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Active>false</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Data</Label> <Letter>D</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>20000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>3</Order> <Type>Logical</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Extend>true</Extend> <Type>Extended</Type> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration>
  8. Hello - wonder if anyone can help me with this. I have added a script to the sysprep folder in vista which basically brings up a pop-up box and asks you to rename your computer. It authenticates in AD and renames it and then reboots the computer - not a problem, BUT! it only runs if I enable the administrator account and use that to run the script. If I use the account I created using XML (which is an administrator also) I just get an error message displayed when I try to run the script. I have added a first logon command into the OOBESystem enviroment which runs this script, so in theory it should pop up, ask me to rename it, reboot and then bring me to the alt ctrl and del screen. I have seen this working in a similar enviroment so I know it should work. It doesn't. I'm guessing thats becasue the admin account is disabled, so it's trying to run the script with the next available account which is my admin account I created ??? ... which if I run manually I get an error code 5 ??? I'm only guessing it's something to do with it not having rights or something to run it. The problem is I can't enable the administrator account! I have read that if you add the autologon part in OOBE and add the username Administrator it should enable the account... I have also read that if you enable it and set the logon count to 1 again... it should enable that account. I have also tried bunging it in different places (Audit System - Audit User) but still it doesn't enable the administrator account. Please bear in mind I'm only guessing it's a security / authentication problem which is why it's not running the script... but it sort of makes sense. Everything else on the XML file seems to work - any ideas ? this is pretty much the last thing I need to get working before finalising the image setup. Any help would be greatly appreciated as I'm getting to the point where this computer I'm testing will leave the office via the 50 foot window and fly gracefully for about 3 seconds, before plummeting to the floor and smashing into a hundred pieces in our reception below.
  9. Hurrah for me! I have pretty much solved it! Just incase anyone else has these types of problems, here's what I did! I exported the image I was working with, and created a new WIM file. I then opened up the new WIM file using SIM and created a fresh Image unnatend file which had been specifically made for that image. There was no differences between the one I was using which failed and this one... and it works. To be honest I just think this technology is just flaky, and If you get it working your just lucky! jimresnikoff Post your XML file up and lets have a look, make sure all the pre enviroment stuff is attached to the Global enviroment and not to the image itself. A couple of pieces of advice would be remove all of it apart from things like the login credentials... and then test it to see if it gets past that stage, then work on from that. I have been working on this bloody thing now 7 or 8 weeks, and only finally got it working today!
  10. I can't get the PC to join the Domain. I get the "Network Settings" box which I believe there is a reg fix for, but instead of joining the domain it's actually creating a workgroup called the domain name... any ideas what I'm doing wrong. Bellow is the XML snippet, it's in the specialise setting (number 4) and I have added this to the image not the global XML file. <Identification> <Credentials> <Domain>mydomain</Domain> <Password>mypassword</Password> <Username>myusername</Username> </Credentials> <JoinDomain>mydomain</JoinDomain> <MachineObjectOU>OU=Default WDS Computer Store, OU=etc etc etc </MachineObjectOU> </Identification> Thanks
  11. Just incase this helps anyone - I removed all the "OOBE" stuff from the global unattended file and created another one called "Image Unnatend" and added the "OOBE" stuff to that ! Worked a treat, installed totally without stopping once. The only thing it did do which i have to rectify is create a worgroup and dumped itself in that instead of joining AD, but I'm sure I can sort that
  12. I wonder if anyone can please help. Banging my head over and over again on a huge Microsoft brick wall here. I'm making an automated unattended xml file... All I want it to do is login to the WDS Server, pick the image i want to deploy (as if I get this working I will have several to choose from) and then walk away! The first bit works, it deletes the HD and creates partitons etc and then installs the image I have chosen. Once it's been deployed I want it to automatically setup the language, accept the EULA, pick the type of network it's joining plus the security setting and then pick the correct time zone. I have read loads on this and really can't see what I'm doing wrong. The XML file below is brand new and created using FireGeiers Unattended Vista Guide. Please help <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" 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"> <SetupUILanguage> <UILanguage>en-GB</UILanguage> </SetupUILanguage> <InputLocale>0809:00000809</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UserLocale>en-GB</UserLocale> </component> <component name="Microsoft-Windows-Setup" 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"> <UserData> <ProductKey> <WillShowUI>OnError</WillShowUI> <Key>*****-*****-*****-*****-*****</Key> </ProductKey> <FullName>My Work</FullName> <Organization>My Work Again</Organization> <AcceptEula>true</AcceptEula> </UserData> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>25000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>3</Order> <Type>Logical</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>2</Order> <Type>Extended</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Vista-OS</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Active>false</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Data</Label> <Letter>D</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> <WindowsDeploymentServices> <Login> <Credentials> <Domain>**</Domain> <Password>******</Password> <Username>******</Username> </Credentials> </Login> <ImageSelection> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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"> <SkipAutoActivation>true</SkipAutoActivation> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" 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"> <AutoLogon> <Password> <Value>********</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>2</LogonCount> <Username>Administrator</Username> </AutoLogon> <Display> <ColorDepth>32</ColorDepth> <DPI>96</DPI> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <TimeZone>GMT Standard Time</TimeZone> </component> <component name="Microsoft-Windows-International-Core" 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"> <InputLocale>0809:00000809</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UserLocale>en-GB</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="catalog:e:/sources/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
  13. OK Solved it But now I have another question The problem was STP was on the switch, option 60 PXClient was on the DHCP scope and thats not needed if the DHCP Server and WDS Server are different physical computers, and the IP Helper wasn't added to the switch... and the last which is the next question I have if anyone can answer it. The computer I have tried to network boot resets once an IP address has been handed out, but it is a computer in Active Directory, another PC which wasn't in AD once I pressed F12 loaded the boot menu, so the question is.... do you have to remove any computer from AD before you re-image it ? I work in a University you see so computers break daily and therefore will need re-imaging alot, but will I have to remove them from AD before you can re-image them ? I ask because I don't think that was the case with RIS Ta chaps
  14. Hi Everyone. I hope I have posted this in the correct place, if not my appologies. I wonder if anyone can please help me with this... I'm going around in circles banging my head against a very big indestructible wall (so it feels) I currently have 2 problems. I have setup a RIS Server (initially) and then installed SP2 / WAIK / WDS and a million other microsoft updates so it's up to date. I have made sure Spanning tree protocol is turned off the ports I'm using (WDS Server and Test PC - not too sure about the DHCP Server but that shouldn't matter as such). I press F12 on the workstation and it starts the PXE boot up cycle, it picks up an IP Address from the DHCP Server... and then when it should open the boot menu - it just reboots the computer. I don't think it's in a "I'm faulty" kind a way, i think the boot menu just isn't loading / being found so it just reboots the PC as it has nothing else to do at that point. The second fault (I don't know if they are related - they maybe ?) is If I use Terminal Services to remote onto the WDS Server, it's really really slow... like you press the start button and have to wait 15 seconds before it initialises... The firewall not on and every other Server I have built and bunged into the Network has never displayed this characteristic. Thinking it was a just buggered... I reinstalled it today, and in the end I have the exact same symptoms. ? Please, any help would be greatly appreciated


×
×
  • Create New...