mrwoberts

One other test... The troublesome SSD in a totally different model/make of laptop; that might isolate whether this is an OCZ of Tosh problem.

Morning. This is a bit of a tricky one isn't, but you've clearly done a lot of testing and can now lay the fault at the feet of Toshiba/OCZ. How about these scenarios, just in case you had so much time on your hands - Flash the previous version(s) uefi firmware to the troublesome laptop - The troublesome SSD in a physically different Pro R50-B - WD40, a large hammer and some gaffa tape - the above suggestions are to be considered dangerous to the health of the equipment and the user; try them at your own risk

Just going off on a tangent a little... Try searching for this sentence in Google "a long time ago in a galaxy far far away"

@koryo Just to be clear, are you confirming that an 'identical' setup (bios version, 64 bit image, memory size...), with the exception of hdd vs. ssd, will deploy as previously described ??

Okay. Were you booting from a DVD or USB; either way, did you force the media to boot from UEFI - bringing up the boot menu (usually F12) and choosing UEFI: Lexar 16GB usb drive.../ UEFI: DVD manufacturer... Also, does your installation media have updates already integrated/slipstreamed, or is this an untouched (iso) ?

Just a few questions... The mechanical HDD that was present before the SSD, did that have a GPT disk layout and Windows x64 installed, together with UEFI enabled? Have you attempted a manual install on the SSD, with GPT, UEFI and 7x64 (you gotta love these acronyms)? The benefits of Windows 7 and UEFI have been asked a lot on the Internet, but I've never really 'seen' the benefits of installing 7x64 with UEFI enabled. I get the impression the later OSes 8, 8.1, 10 make better use of the UEFI implementation.

Let me run this past you to make sure I've understood correctly. A user signs on to a domain PC using personal credentials. A new (temp) profile is created using that PCs default ntuser.dat hive and appdata folder. Some registry settings or appdata for specific software is 'missing', or insufficient. You'd like to add these missing registry settings or appdata to the PC. Once that works you'd like to roll this method out across all domain PCs so that each login is quickly created from the 'default' profile of the PC in use. Assuming the above is correct there are possibly some steps I can help you with, but you may already be doing them... Such as, to make changes to the default user hive I would load it into the registry, import the changes you require, then unload the hive. For example... REG LOAD HKU\DefaultUser "C:\Users\Default\ntuser.dat" reg import defaultUserSettings.reg reg import ieDefaultUserSettings.reg reg import mplayerDefaultUserSettings.reg REG UNLOAD HKU\DefaultUser You then have a default ntuser.dat hive that I believe is transferable. NOTE: Your defaultUserSettings.reg files would have to point to the correct key, as in... [HKEY_USERS\[b]DefaultUser[/b]\Software\Microsoft\Windows\CurrentVersion\Explorer\VisualEffects] "VisualFXSetting"=dword:00000003 I have tried this approach in the past, but there were one or two things I couldn't achieve with this approach, to do with IE 11, and Media Player. I discovered that was because they each go through an initialisation upon first login. To get around that I put a silent .vbs script in the Default Users startup folder, which imported the REG settings then deleted itself - errors were logged and suppressed. For the AppData contents, I simply copied the necessary folders to the default user profile, creating the subfolders that didn't exist... I had no problem with that part, as it was copied as expected during new user creation. Am I on the right track?

Okay. On the original disk, were there any other partitions, which you didn't copy across. Possibly name, 'System Reserved'. Unless you explicitly forced Windows to install without a System Reserved partition, then you will be missing the boot loader. Try cloning the disk, at least with the reserved partition, or you'll need to attempt to create the boot loader folder (\boot) on the single Windows partition. Let me know which you want to do.

Can I just ask, does the original hdd work as normal, following the partition changes? Did you clone the entire disk HDD -> SSD, or just the main windows partition?

Could you provide more details... How did you create your default user profile? What do you want to happen when a user logs onto the machine? Will that profile be erased when they log out? Do you want pre-generated appdata to already exist in the default user profile when a new user is created? Detail exactly what you want to happen, including the pieces of the puzzle that you don't have - what would they look like?

You need to change the X:\ part with the correct drive that has the windows folder on it. If you're not sure, then you'll need to 'check' the first few drives like this... if exist "C:\windows\." echo FOUND windows folder! if it doesn't find it, try the next letter if exist "D:\windows\." echo FOUND windows folder! and so on...

You typed, dism /image:X:/ /get-packages Which is incorrect. The correct version would be, dism /image:X:\ /get-packages Notice the 'backslash' after the X: Also, it looks like you were not typing the command as detailed above. Type it exactly as below and then report the results. dism /image:X:\ /remove-package packagename:Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1 /scratchdir:%TEMP% REPLACE X:\ with the drive letter that corresponds to your Windows installation. For example, it may be C:\ or D:\

I'm dreading the move to Windows 10 with its 'no questions asked' approach to windows update. Am I right in thinking that only the Enterprise version of 10 can be told not to automagically update windows??

That depends... Just to be clear, you are using a standard pc, Windows 8.0 os, and running a script (.bat / .cmd) to remotely shutdown pcs across your network? Do you have an identical admin account on this Win8 pc, to the rest of the target pcs? The password must also be the same, and that account must not be disabled on the target pc. If you can access the pc using interactive credentials, then try saving those credentials in your credential manager, or try the /savecred option with the 'net use' command. if these pcs are on a domain then I'd lean towards controlling these PCs from your Domain Controller. Alternatively, investigate the route mentioned in responses above and create smart schedules for power schemes... I know you say this has worked in the past, but I never rely on that kind of logic, as you and I both know that things always change whether you are in control of it or not.

Where are issuing these commands from? A cmd prompt on the DC ? What happens when you attempt to access the machines C$ drive? e.g. net use * \\test-pc\C$ Did you try the ipc connection I mentioned in an earlier post?

That makes sense. If you wanted to explore that option you could use WakeOnLan, which can also be used to wake machines up in the middle of night to carry out certain tasks...

@GuyJD Just curious if you have a third power profile for holiday (school closed) periods?

@GuyJD Nice idea, thanks for sharing. To be honest, the cost savings of shutting down pcs are minimal nowadays. I did some research and tested physical machine power usage when in use, asleep, shutdown. I discovered that most machines, including the monitors, barely used 1w when asleep. As you say, forcing a shutdown can cause other problems so I opt to sleep machines.

What happens when you connect to the ipc first? net use \\test-pc shutdown /s /t 60 /m \\test-pc /d p:0:0 As an opinion, I might prefer to sleep these pcs, but you may need a separate app for that.

I love a happy ending. Thanks for sharing.

Looking at the Intel Download Center for DB75EN https://downloadcenter.intel.com/product/59043/Intel-Desktop-Board-DB75EN The USB 3.0 drivers are version 1.0.9.254 (10/16/2013) Did you use those drivers?

@googlemad I've had this same problem on a bunch of RM laptops - bluescreen after install of USB 3.0 drivers, but appeared to be installed afterwards. I worked out that it was something to do with my image, and if I tried a vanilla install, no windows updates... and installed the drivers straight away then it worked. Rather than spend countless hours hunting down the root cause I decided, like yourself, to remove the drivers, install the Standard USB drivers (treats it as usb 2.0) and have done with it, but I'm just as annoyed/curious as to why that happened. It might just have been a coincidence, but I updated the BIOS on one of those RM laptops and I think that particular one didn't then have the bsod problem?? Worth a try if your BIOS already needs updating.

If you are with RM SafetyNet, have a read of this (Google SSL interception changes) Changes to Google SSL and RM SafetyNet | RM Education - What we do

One other thing. If you installed these machines from a stock Windows DVD and let Windows Update do its thing, then I would run 'Disk Cleanup' as Administrator - this should cleanup possibly over 1 GB, but is good housekeeping anyway.

If you don't need to hibernate these machines then remove the hibernation file (hiberfil.sys) powercfg /h off If you have other ways of recovering from errors, or system file corruptions then switch off the System Restore. Depending on how much Physical RAM you have installed you could look at the MAX size of the Pagefile and reduce that to say, 2048?? Perhaps also adjust the Recycle Bin sizes, or better still choose the, "Don't move files to the Recycle Bin. Remove Files immediately when deleted." option.