ces973 Posted December 15, 2009 Posted December 15, 2009 Only does that if you use the /generalize option which he is not. Well, there goes that idea. I know we use the /generalize option, but we have our answer file set up so that it doesn't remove any drivers.
jmcdermott Posted December 15, 2009 Posted December 15, 2009 How about switching the bios setting for the sata and seeing if that helps, would just be for testing but worth a shot.
pritchardavid Posted December 15, 2009 Author Posted December 15, 2009 (edited) havent got the sata option in the bios maybe that the problem then like I just said i just used the command line above from ces973 with had generalize in it, didntt reliease it was different So I should have tried you batch file instead with admin rights this time? has last time I used your batch file, it didnt work Edited December 15, 2009 by pritchardavid
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 ok just tried your guide again, with UAC off and just the batch file (Even ran has admin in case) Still does not want to find the hard drive! I have had the hard drive show before on the old sysprep I edited from this site Sysprep a Windows 7 Machine – Start to Finish - Blog.BrianLeeJackson.com With this command line has shown in that guide above sysprep /generalize /oobe /shutdown /unattend:NAMEOFYOURANSWERFILE.xml Is it it me, could the sysprep file somehow not making it work? Most sites tell you to use the generalize command for it to work, im getting confussed whats the difference in use that command and not using it Gonna reinstall windows 7 yet again, not configre anything, see if its what im configuring is causing the problem, if its not thta, im gussing there is something wrong with the command or sysprep file
jmcdermott Posted December 16, 2009 Posted December 16, 2009 As far as I am aware the /generalize option is used to wipe out the Hardware database from windows, If this is done windows is forced to re detect all hardware on next boot. The only advantage I can see with this is that you could send out the same image to multiple machine types instead of having a different image for different hardware. Having previously been trained by Viglen to sysprep older machine with the /pnp to wipe out plug and play devices, and then seen all the issues caused by this process i always advise against it. Sorry my method didn't work for you, I have had it working perfectly here for the past month with no problems.
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 well its working now used the generalize command, changed no settings what so ever, and it worked! So its some of the settings I was doing was causing problems Things I was doing Customize Internet Explorer and Windows Media Player Settings Disable System restore Change user temp folder locataion Disable system failure, startup time, in systme properties Enable remote desktop connection Disabled sync Copied user icon and desktop picture to main root of c drive and appied these for the user Disabled some uneeded serivces (net framework, windows search, http web proxy, media player service, ssdp discovery, shell hardware dedection, windows defender, security centre And also copied the account user account I was cutomizing and has the default profile
jmcdermott Posted December 16, 2009 Posted December 16, 2009 Very strange, well if it works it works.
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 ok maybe not its got so far in sysprep and up popped a lovely error box Windows could not parse or process unattend answer file [C:\Windows\Pather\unattend.xml] for pas [oobesystem] The settings specified in the answer file could not be applied. The error was detected while processing settings for companent [Microsoft-Windows-Shell-Setup]. Any idea guys my answer file looks like this en-UK en-UK en-UK en-UK en-UK true true Work 1 PASSWORD false PASSWORD false Local Admin The Ockendon School Administrators The Ockendon School UTC false PASSWORD false true 1 The Ockendon School
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 (edited) Ok just printed out your one you sent me and the one I had edited Only difference is the passwords and usernames of course, but best to check Username I put The Ockendon School Username you put was Build_User Does It Like spaces? Think that is what is causing the problem? Also just to tell you where you add the local user, you wrote administrators wrong, your missing the r Edited December 16, 2009 by pritchardavid
jmcdermott Posted December 16, 2009 Posted December 16, 2009 Cheers for pointing out my error fortunatly it does not seem to make a difference to any thing, as far as using a space in the username, i am not sure i seem not to, and everyone else in the office here has no idea, think it is one of things just never tried. Looking at your command line "C:\Windows\Pather\unattend.xml" is this where your unattend.xml is stored?
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 nope it is in system32\sysprep so im finding that weird Unless sysprep moves or copy the files to there when it start the sysprep process
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 ok reinstall yet again try the username has ockendonadmin instead of the ockendon school That way there is nno difference in our files, there should be no problems
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 nope still didnt work, maybe another try and also copy the syprep file to that pather location to make sure this is really getting on my nerves now Any more sugguestions would be great guys if you can
pritchardavid Posted December 16, 2009 Author Posted December 16, 2009 ok that did not work eithier must be something wrong with the sysprep file any other ideas, other than that guys? If anyone has a sysprep handy, could they email it to me at davep @ live . com so I can look at it or maybe edit it for our settings
pritchardavid Posted January 5, 2010 Author Posted January 5, 2010 jmcdermott need you help please or anyone who understands this I have the following problem on your power script file I have made my required images, when I tested the image, your script did not seem to add the computer to the network I didnt disable UAC (Forgot to) So to this the script with admin rights, I lanched CMD with admin rights and lauched the script from that The following error came up. File add2dom.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details. Did you get this problem? Dont really want to manually add the computers to the domain after imaging a computer everytime
pritchardavid Posted January 5, 2010 Author Posted January 5, 2010 never mind, me being stupid, noicted in your batch script, you have elevate execution, so yer defo need UAC disbled Left the 4 laptops creating the image Yep 4 One for 64BIT Workgroup (For Staff Laptops Normally) One for 64BIT Domain (For Student PCS) One for 32BIT Workgroup (For Staff Laptops Not 64BIT CPU) One for 32BIT Domain (For Student PCS Not 64BIT CPU) All domain images only have settings I want applied, no software installed expect updates, Software Distribution installs the software for the domain computers
jmcdermott Posted January 6, 2010 Posted January 6, 2010 Yes the run once script enables the execution of scripts before it runs the addtdom.ps1 script.
pritchardavid Posted January 6, 2010 Author Posted January 6, 2010 Umm ok another problem seems to have arised, it seem after I sysprep the 4 machines again, that I was using to make the image (Needed to change a setting) It seems that it came up with the OOBE setup screens Does this happen when you sysprep it a second time? I have seen that you can add the unattended file for the image on the WDS console, under the propeties of the image, would this be a better way of applying the images part of the install? I did try this (Still had the old unattanded file from the image enable, so dont know if this was conflicting. Has when I tried it doing this way, it seems that it add lots of US language parts to the system and the lanuage bar came up (Dont want that) Really need to know if sysprepping the same image again would cause problems
jmcdermott Posted January 6, 2010 Posted January 6, 2010 I think you can sysprep a machine up to 4 times before problems start to occur. As long as the unattend file is still in the same place it should just do the same thing as last time. As for using WDS I found the whole process to be to much of a pain in the rear so stopped using it and switched to a free imaging suit called FOG which is much easier, so can not comment on using the unattend file with it.
pritchardavid Posted January 14, 2010 Author Posted January 14, 2010 on your region settings, is yours all usa? Seems when I instal lmy image thats the settings I get, I used the same wording has you used for the language settings
pritchardavid Posted January 14, 2010 Author Posted January 14, 2010 thanks mate, i'll edit that tomorrow then about the system local is that the same, or do I have the that that number code if you know what I mean
DMcCoy Posted January 14, 2010 Posted January 14, 2010 My section for vista is below so it should be virtually the same in 7. en-GB en-GB en-GB en-GB en-GB
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now