Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mobious99

Profile Information

  • OS
    Windows 10 x64
  • Country


  • Country Flag
  1. Hi Everyone, so I have everything working with all of my images and everything is going well but lately I've noticed that the images (physical or virtual) all seem to reset their windows updates to be missing updates after the cloning process. for example: - 3 virtual machines cloned from the same template (in this case 2008 r2) The first machine - 38 missing updates The second machine - 62 missing updates The third machine - 40+ missing updates has anyone seen this behavior before? Fyi, every month I update my images on patch Tuesday to avoid the stuff from above if possible. I get the same results btw from above with my physical server images.
  2. I looked at the winbuilder project and I wish I could use it but I was looking for more of what files / directories need to go where in the build. I just wanted something simple like these files need to go into these directories and then I could build it from there.
  3. Hi Everyone, I've ported my 32 / 64 bit versions of winpe over to 8.1 but I was wondering if anyone has any directions / pointers for getting syswow64 support into 64 bit? The problem that I currently have is that the vendor has stopped making 32 bit drivers so I need to be all 64 bit but w/o any syswow64 support I'm stuck. any help would be appreciated.
  4. I'm going to add this to my startup script rem remove system reserved drive letter diskpart /s removehiddent.txt removehidden.txt has the following lines in it.. SEL VOL 0 REMOVE LETTER=D Where d: is the drive that always gets assigned to the system reserved partition. It's got to be something sysprep / winpe is doing because when I boot off my winpe cd I see two drive letters.
  5. I actually tried something today - imaged a 2008r2 device - removed the drive letter - rebooted - boots no problem. no idea why this is adding a drive letter.
  6. yes the image is. I only capture the windows partition not the system reserved partition, I'm thinking about doing that next and then recreating the boot files. I've also tried not assigning a drive through diskpart and the drive is still getting created.
  7. I took out the drive letter for the system reserved and it's still assigning one on bootup. it's just strange that diskpart script is right from microsoft. the w: drive changes to c: on bootup.
  8. I'm using imagex to do the deploy. here's how I'm doing it - boot into winpe - map drive - run diskpart script - standard script from microsoft select disk 0 clean create partition primary size=300 select partition 1 format fs=ntfs label="System Reserved" assign letter=S active create partition primary size=102400 select partition 2 format fs=ntfs label="Windows" quick assign letter=W active exit - Then apply the wim file to the windows partition imagex /apply f:\2008r2\2008r2ent.wim 1 w:\ - Then run these commands to make the device bootable bcdboot w:\windows /s w: bootsect /nt60 w: after that re-boot and off I go.
  9. thanks for the help guys. I've decided to move all of the apps that won't install under all users to post deploy and copy any shortcuts to the allusers shortcuts. I wish there was a way to verify that the default user profile and what was copied.
  10. I'm using an answer file, and then capturing the image with gimagex. I've only been capturing the windows partition.
  11. has anyone found a way to get the system reserved partition to create w/o assigning a drive letter to it? I'm trying to get the install so that it looks like a standard windows install and cannot for the life of me figure this out. I've even tried this on the volume - in the pre and post configuration. diskpart sel disk 0 sel vol 1 attributes vol set nodefaultdriveletter
  12. yes they exist under default admin account I created but not all users profile.
  13. allot of the custom shortcuts, and only parts of the desktop seem to copy. is there a better way of doing this to assure all settings get applied?
  14. updated. strcn = InputBox("Change Name to the following","Please Enter Computername", compname) Name = strcn name= UCase(Name) If Len(name) > 15 Then Wscript.echo "The name is too long for use with wins" wscript.quit End If If Len(name) < 1 Then Wscript.echo "The name is too short to be used" wscript.quit End If Set objRegEx = CreateObject("VBScript.RegExp") objRegEx.Global = True objRegEx.Pattern = "[^A-Z0-9]" strSearchString = name Set colMatches = objRegEx.Execute(strSearchString) If colMatches.Count > 0 Then Wscript.Echo "The following characters are not allowed:" For Each strMatch in colMatches Wscript.Echo strMatch.Value wscript.Quit Next End If strComputer="." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colComputers = objWMIService.ExecQuery ("Select * from Win32_ComputerSystem") For Each objComputer in colComputers err = objComputer.Rename(name) if err <> 0 then wscript.echo "There was an error renaming the machine. Please restart, and try again." else wscript.echo "Machine successfully renamed: " & Name end if Next
  15. Hi Everyone, has anyone ever gotten the copyprofile option in sysprep to work for all shortcuts / settings? I have hardware independant images that I build on virtual machines and then sysprep after they've been snapshot. the way I have them built is - standard os install - standard software suite - temporary admin account used for the build (all software installed under that user) - desktop tweaks applied to default administrator and to the temp admin user - after completed and qa'd I run sysprep /audit to inject the drivers. - upon reboot I then run sysprep /generalize etc etc. so shouldn't all profile settings from the temp admin user be copied to the default user account and any others?
  • Create New...