mikerowsopht

Member
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikerowsopht

Profile Information

  • OS
    none specified
  1. HI All, I have an issue with Group Policy settings not being applied / not working on my windows 7 client. The server I am pushing out Group Policy is Windows 2003 server and the client is Windows 7 32 bit Enterprise. I think that because these OS's aren't part of the same family that Windows 7 isn't working correctly when I push out Group Policy settings from the windows 2003 server. Basically I am trying to turn on a few simple settings such as : Remove all icons from Start Menu - can do this Remove Taskbar - can't do this Remove all icons from desktop and run only 1 program on startup - this works but if I click on "Show Desktop" there are no icons however if I minimize the program that should be running I can see all icons on the desktop and access them as well as My Computer etc... etcc.. The Group Policy settings are fine ( I think ) but Windows 7 doesn't seem to like these settings from Windows 2003 server. I have been told / read somewhere that I might need some sort of ADM or ADMX files in order to get Windows 7 working correctly with 2003 server GPO. What I am wondering is can anybody at all shed any light on what exactly I need to do in order to get the settings to be applied correctly so : 1) - Do I need these ADM / ADMX files ?? If yes where can I download them from and where do I install them, eg - the client or the server ? 2) - Any other insight or anything I've left out that you think may be of assistance to me that would be much appreciated. Thanks ALL !!!
  2. I have just tested this coz I'm bored, installed the sms client onto a pc, sysprep'd & captured it, deployed it to 2 pc's and tested it on the domain. SMS reports both of these machines as separate and it does not show up as 1 pc as stated above because of the SID. So der ye go ( although I am sure the statement above is correct and is best practises from microsoft ) No doubt there is software that use ClassID's and the old sid before sysprepping Also here is a link from the technet site regarding the SMS Advanced Client & sysprepping : http://technet.microsoft.com/en-us/library/cc181430.aspx Installing the Advanced Client on a computer master image You can load Advanced Client software components on the computer when it is originally prepared for service in your organization. Typically, computer preparation work is done by an IT team in a staging area. The Advanced Client is installed on a client computer master image by installing core SMS client components without specifying an SMS site code for assignment. The computer is ready to be assigned to a site when it arrives at the location where it is used in production. The master image with the SMS Advanced Client is automatically configured with an SMS GUID when SMS is installed. The Advanced Client detects that the computer has been prepared from a master image and creates a new GUID. This prevents duplication of SMS GUIDs on client computers when the Advanced Client software is loaded on computers before the computers are put into service in your organization. Important: Because a Legacy Client installation to a master image cannot detect that the computer was prepared from a master image, the SMS GUID must be removed from the Legacy Client before the computer is removed from the staging area and placed in service. This can be done manually, preferably in the master image, or it can be done by the Windows System Preparation tool (Sysprep.exe).
  3. Where's the help :-( Here's the answer to the above Q : btw this is only for XP service pack 3, if you have XP SP2 ( I think ) you don't need to do this as it happens automatically but I haven't tested it on a SP2 build and never will. Basically if you add the below ( Bolded & underlined ) into your sysprep file it will copy or move the local Admon account which is created during sysprep into the administrator account and as such removes the Admon account which has no password set because of sysprep ;SetupMgrTag [unattended] InstallFilesPath=C:\sysprep\i386 UpdateServerProfileDirectory=1 [Guiunattended] EncryptedAdminPassword=No [userData] FullName=Admon OrgName=MyOrg
  4. Well your sysprep.inf file is obviously on the C drive of your captured pc, otherwise you would not have been able to capture the image if it wasn't sysprep'd However if it's asking for the product key, eula etc... maybe you put the wrong product key into your sysprep file using a single license instead of a mvlp license ? or Did you create an unattended.xml file that you have attached to the captured image in the WDS console, if so remove the xml file and try to deploy the image to a test machine and see if it works, The xml file automates the installation but so does sysprep and they could be conflicting,
  5. I also install the sms client on client computers on the network for reporting before sysprep and after it's on the domain, doesn't cause me any problems.
  6. When you sysprep a pc you have the option to re-generate the SID regardless of whether or not the pc is added to the domain or not. Best practises say to remove the pc from the domain before sysprepping but it doesn' t really matter in my experience. The sid is re-generated when you run sysprep and select mini setup and reseal ( regenerate Sids ) Also when you name a pc the Sid is also regenerated so when it goes on the domain and you name the pc the sid is also re-generated. And Also according to microsoft sysprep removes the pc from the domain if it's already added. Bascailly I add the pc to domain, sysprep it which re-generated the SID, during sysprep I specifity to add it back to the domain. When deployed the sid is regenerated, the pc is added back to the domain again and because the pc was already on the domain it all all my apps, wsus updates, gpo settings on it, has everything. I do this all the time and never ever have any problems at all
  7. Hi All, This is the last problem I have with deploying XP via WDS although this is more of a sysprep problem I think instead of a WDS problem. My XP machine that I have built for capturing is added to the domain, thought I would mention this first as people say to remove the pc from the domain before capturing but sysprep removes the domain anyway and it doesn' t cause me any problems once the SID is re-generated and the pc is named. My problem is that basically I set a password for the local admin account, lets call the password "password" During Sysprep I am asked to create a local account, if I do not create one it will be automatically created for me, I cannot name this account administrator or Guest. I usually create a local admin account called Admon with a password of password. What is happening is after the pc is finished being deployed and ready to use I can log onto the pc locally with username Admon and no password at all ! If I log onto the pc locally as administrator and use the password "password" I can log in. So bascially the passsword I am setting locally for Admon is not working and sysprep is using this passowrd and applying it to the local Administrator account instead. Realistically I don't even want the Admon account there and would prefer to set the password for administrator which it won't allow me to do. I don't want to delete the admon account every time I deploy an image Has any1 ever come across this before, it's really annoying ! Thx All
  8. Ok I have figured it out so might as well share it with everyone. Don't name the pc in pending devices on the WDS console, it doesn't work if it's XP. Just approve the image. While sysprepping the XP maching select generate a random computer name during setupmgr. Once you have finished creating your sysprep.inf file open it with notepad and remove the * from computer name was : computername=* now computername= this confuses sysprep during the deployment and it pops up and asks for the PC name and local admin password at the client. Once you enter these details your pc will continue to install automatically with the pc name you have given. You are however able to approve and name the pc for vista / win 7 I wasn't really bothered created mysysprep2 ..............
  9. Got it working for xp in pending devices now I can name & approve the image from WDS deploy xp again I get a random name even though I named it in WDS console during sysprep I can only select 2 answers for the name which is a random name or somethng else which doesn't apply it's obviously getting the name from the sysprerp file, I have even removed the code from the sysprerp file to give the pc a random name grrrrrrrrrrrrrrrrrrrr
  10. No worries, thnx again for your help, think everything is going well now, I have started a different post in relation to Windows XP & pending devices here : My link XP won't show on pending devices whereas vista and 7 do. XP doesn't however.
  11. Hi All, I am having a couple of issue's with WDS and XP. WDS is setup and working correctly with no problems. I can deploy windows 7 to a pc and it shows up in pending devices which I can then approve and name the pc. When I deploy XP the pc does not show up in pending devices and instead gets a random name. The WDS server does not have an unattended.xml file for the boot image, only for the install images. Before capturing the image of XP I did sysprep and created a sysprep.inf file on the root of the C drive. I have opened this sysprep.inf file and see a computername option with a * in it for ramdom naming. I have removed this line from the sysprep.inf file so there is now no computername in the sysprep file. When I deploy it again it still gives itself a random pc name and does not show up in pending devices. I am confused at this point as I have removed the naming from the sysprep.inf file. I know everything is setup correctly on the WDS side because I can deploy vista and Win7 with no problems and they show on pending devices. When I deploy XP it doesn't show up on pending devices on the WDS server. Does anyone know what I have to do to resolve this ? Do i need to create a unattend.txt for xp instead of sysprep as when I click on sysprep.exe I have a choice of xml file or sysprep.inf Basically all I want is for my xp image to show on pending devices so I can name and approve it, then I would be a happy man. Thnx All you Wise Folks ============================================================================================== editied by me : Just to note I have sysprep'd the xp machine and it is added to the domain, then I did the capture. Should I have removed it from the domain before capturing and that is why it is not showing up in pending devices, not sure ???
  12. it's an odd one alright. I have multiple separate images, no base images. I have checked the size of the image itself in remoteinstall folder under images. If I right click and go to the properties of the wim file it is only 2.6 gb if I switch back to the WDS console under image group and look at the images in the deployment section it reads 18GB !!! Odd considering it's the same file. As long as the real file doesn't grow hopefully it shouldn't cause me any problems. I just don't want to end up 6 months down the line with a image size of 40GB and growing
  13. No worries, I work in an Enterprise environment anywaz.... Everything is working now so thnx for the help. 1 thing that is bugging me though is the size of my image.wim which is constantly increasing in size which I only realised recently. For example I built a pc with with windows 7 and all the company's apps, captured the image and uploaded it to wds and have used it constantly on the same pc ( vm ) for the last few weeks. I backed up the orignal captured image and confirm that it is 2.6GB once captured. I have deployed this image roughly 20 - 30 times and the on the wds server in the console the image.wim is now 18GB !!!!!!! This is insane ! If I deployed this image to over 100 pc's over 6 months the image could be massive. Any ideas why it does this ? I have never exported the image or mounted it or edited it with imagex or any third party tool. When I created the xml file with waik origianlly it was done with a copy of the image.wim not the one on the server that I use to deploy. I have deployed a couple more pc's and watched the size of the image.wim and it hasn't increased any more so it seems to be random. Any Ideas ? Nothing on Technet and only 1 link on google but that guy was editing his wim file and I am not.
  14. Hi Tripredacus, thnx for the info again, I have purged the WDS database and can now re-deploy the same image to the same pc over and over again ( for testing purposes ) with the link you have provided me. When I get back to work in a few days I will test out the Public option for "set network location" The server I am using for WDS is a windows 2003 server but that has the same bug for purging the database in WDS , we plan on setting up a new win 2008 server once I am happy with all the testing. I believe win2008 has extra options in the wds console such as packages and drivers. I still haven't got around to using MDT2010 but will be downloading it soon to see what it can do for me. Currently I am just using WAIK which is all I need right now. I didn't realise you needed a license for MDT2010, thought you could just download it from microsoft and install it and use it ?? mdt2010 download is here : MDT2010 thnx again, I appreciate your help & guidance
  15. With the link you have provided me with I have got everything working bar 2 things, thanks very much for your help ! 2 things are this. First screen I see during bootup is the UI language & keyboard layout even though it's specified in my xml file as en-ie If I switch it back to the default en-us it doesn't pop up during bootup If i switch it back to en-ie it does pop up. I cannot seem to download a language pack ( en-ie ) to insert into the wim file for windows 7 perhaps the xml file needs this en-ie folder to set the language? It doesn't matter anyway as I have set it back to en-us and it doesn't pop up, once the captured image gets deployed it comes down as en-ie as that is how I captured it so that part doesn't matter to me I suppose. The last thing I find very irritating is when the pc is finished being deployed I log in and the "Set Network Location" dialog box pops up and I select the "Work" option. It says windows cannot set the network location and I hit close. I believe from a bit of research that this is a bug in windows 7. Even though I have specified the answer to this in the xml file it doesn't apply it and the box pops up. Do you know by any chance of a bit of code to insert into the image xml file that will bypass this? or can I disable it altogether in the registry before capturing the image of the pc so it doesn't happen to future deployments? preferably an xml option but I don't mind. Last thing is pending devices, I got this to work, approved the pc for deployment and named the pc. It popped up in the OU and was created, everything worked great. If I pxe boot the client that was just imaged it fails to install the image, if I turn off adminitrator approval in WDS it works. So i have delted the pc object in AD and waited 30 mins, re-dployed and it still doesn't work. Is there some restriction on deploying pc's that you can only deploy it once or why would this happen ? Something must be created in AD apart from the pc object or similiar thnx again Mikerowsopht