Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stephensr

  • Rank

Profile Information

  • Gender
  • Location
  1. Wooohoooo Resolved this.... Went back to basics, re-created the unattend file in SIM and set the UILanguage to en-US and all is working grand!!
  2. Additional Language Pack…. I’m deploying W7 X64 Enterprise using SCCM 2007 with MDT Integrated (zero’ish touch), no problem there at all… Standard setup en-GB throughout however a requirement has arisen to include the zh-CN (Simplified Chinese) Language Pack for one of our regions. en-GB is to remain the standard but zh-CN needs to installed as an option for the users in that region. The language pack installs great apart from one annoying thing and that is the language option screen in OOBE, the damn thing keeps appearing and it’s driving me nuts! Please see attached file.. I
  3. Hey hotdog453 Did you ever get this resolved? This has presented itself in my environment when everything was fine. It's not consistent which is driving me nuts... Thanks Rich.
  4. Hi there... Yes you are correct...the blue screen is occuring because the pointsec pre-boot sector is referencing data on the drive that no longer exists... Are you re-sizing the partitions? I'm pretty sure that hard linking on an encrypted disk is not possible if you are resizing the drive... we are using a State Migration Point to store our backed up data.... because we resized the partitions I had to break the refresh senario into two phases using two task sequences on encrypted laptops.. 1st ) A simple back -up TS which runs USMT and stores the data on the SMP 2nd) A d
  5. Morning All… I’m looking to use the Pre and Post OEM Task Sequences in SCCM 2007 R2… I have successfully got these two task sequences working on the same physical system. The Pre OEM Task Sequence installs the captured image and core apps and then runs ZTIOEM/Pre to place the breadcrumb files and set the partition to inactive.. .the same system is then pxe booted and the Post OEM Task Sequence is run. This applies the system name, drivers, install system specific apps and joins the domain, everything works as expected. The problem I have is capturing an image of the system once
  6. Morning all, I’ve been looking at an issue for the last couple of days that has me somewhat confused. I know there have been other posts regarding this but I’ve not yet seen a definitive reason behind it… We have a small number of systems in the environment that have two physical drives for example a 75GB and a 300GB drive, meaning the preferred setup would be: Disk 0 (75GB) 200 MB: System reserved 50GB: OSDisk 24GB: Data Partition Disk 1 (300GB) 300GB: Extra Can someone please explain why in Win PE these disk randomly swap between Disk 0 and Disk 1?? I need
  7. Bronx Bull, I've been working away in the lab and after a few teething issues with DMU compilers I can confirm that with the filter drivers injected the TS is working fine on the Encrypted systems! If I am ever in Upstate NY I owe you a beer or two!! Thanks-for taking time out to assist, really appreciated! Issue Resolved! Rich.
  8. Morning Bronx Bull The OSDStateStore sounds interesting, although because the whole drive is encrypted I wonder if this will still work. Because the TS is running a Refresh(Wipe & Load) it is being run from within the OS… I don’t think you can diskpart the C partition when the OS is running… I totally agree that USMT isn’t the issue..and yep like your TS I have UMST loadstate is in the tail end of the TS, which works as expected. This TS including USMT works absolutely fine on un-encrypted systems, it’s purely the encrypted laptops that are causing the issue.. From the image
  9. Thanks for your response Bronx Bull…. 3rd party Encryption and OSD really don’t play nice and it’s giving me a bad headache! ;-) All packages are being run directly from the DP’s however when the TS runs it automatically stages the TS config files (_SMSTaskSequence) to a local drive, then boots to PE and references the _SMSTaskSequence directory… I think re-directing the staging directory to a network share sounds like it could get really quire messy, if as you say it is even possible. I will investigate further… I have heared about the Checkpoint filter drivers but from what I h
  10. Morning All, any ideas on this one would be greatly appreciated. I am deploying our captured image using one task sequence that caters for the Bare metal and Refresh (now Wipe & Load I believe) scenarios, this has worked fined until we perform a Wipe & Load on the Checkpoint Encrypted laptops in the fleet. These laptops have all partitions encrypted leaving no un-encrypted estate on them. You may already see where I am going with this…. The task sequence is being advertised to the user who runs the TS from within Windows enabling the capture of USMT data to the SMP. Once th
  • Create New...