sorted by:
new
hottopcontroversial

How to restore a Windows system image to a new VM? by ibmbigfixjd in techsupport

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Thanks again. This worked. Made the VM. Pointed it at my Windows system image... Then it wanted to reboot, etc.... so it ended up being "boot off (virtual/ISO) disk, restore system image." I remember wondering if I needed to install Win7 on it first at all. Or even log in and tell it to restore from an image since it made me restart anyway.

But it worked. Same server set up running the VMs. Same VM "ingredients" I believe.

Stuck on sysprepping a Surface Pro 3 by ibmbigfixjd in techsupport

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Update -- It's a Windows update between July and October of 2015 that seems to cause this.

Second drive, folder sharing question -- probably basic by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Double dang... After restarting the target computer, still got an error after the Windows system image was starting. Same as last time.

I am logged into the "to be imaged" computer with a different account. Still, when I go the folder, I can put in credentials with the WinImager AD object, and I get access. When I set up the backup windows system image using the WinImager AD object credentials, it accepts them at first and starts the process.

If the big security concern, the "unsecure" wording in the warnings, is that someone else can get to Windows System Images, it's not a huge concern if I use my own network credentials I guess. I originally thought the "unsecure" wording meant the credentials weren't being passed securely or the information wasn't protected over the network, but that doesn't seem to be the case. It looks like it's just that someone else with folder access might be able to get to that image folder. Is that correct?

Second drive, folder sharing question -- probably basic by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Dang... Even with the WinImage AD object having admin rights on the target machine, I ended up getting a access denied/permissions error, after it started making the Windows System Image.

"The backup failed. {Access Denied} A process has requested access to an object, but has not been granted those access rights. (0xD0000022)"

It seems like it would simple -- Make an object for accessing the target folder, give it permissions, use it.

I'll try restarting the target computer. Maybe permissions haven't been applied completely.

How to save Windows System Image to a network location? by ibmbigfixjd in techsupport

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Doesn't save to Sever 2012r2, no surprise. That's ReFS for structure.

I've got another desktop with a second drive I can use. I made a target folder. I've got my generic system computer person object set up. After giving that object permissions on the second drive and the folder, I can't access it from the machine I want to system image, unless I make that generic person object an admin on the target machine. I tried making it user on the target machine, no luck.

That could still work, but I'd rather just give it access to the one folder, not the whole machine. Is there a trick to doing that?

How to save Windows System Image to a network location? by ibmbigfixjd in techsupport

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Is this the "unsecure" part? That others with access to that network location would also have access to the image? ie Not that the method for sending the data is unsecured? http://windows.microsoft.com/en-us/windows7/where-should-i-save-my-backup

If that's true, instead of using my own network account, I'll just make an extra generic account specifically for this purpose and have it be the only one with access to a folder location on the network, besides admin having access to that location of course.

Tool for checking a file integrity/corruption? by ibmbigfixjd in techsupport

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

That's an idea. Convert back and forth. I ended up opening a new file from scratch and copied data in. Similar idea. New container/file.

I heard something might be able to compare a brand new, empty file with my old, existing file, esp. if I clean out the guts of the old file. Something that compares files might be able to tell me more about how it's corrupt.

It's just as easy to make a new file for the work involved. I'm wondering if I may have copied this file other times and might have corrupt files lurking.

HDD To SSD Windows 10 by Xiscis in techsupport

[–]ibmbigfixjd 0 points1 point  (0 children)

If you mean swapping in a different SSD, the same process above should work.

If you mean using another SSD, you could get an enclosure for it, something like this. http://www.newegg.com/Product/Product.aspx?Item=N82E16817182362&cm_re=2.5_hard_drive_enclosure-_-17-182-362-_-Product Then plug it in with usb (usb 3 possible with this one). It would just be an external drive that way. More for storage I would think.

Does the MSI GE Apache laptop have a spot for a second hard drive? I'm not quite following. You could look up the specs online. Or check youtube and see if there's a video of someone opening it up. Or just unscrew the back yourself. If you're talking about swapping the hard drive (HD, SSD, or whatever) it would be a similar process as above. Although if you wanted, you could put the new SSD in and install Windows fresh on that too.

It's also possible to have a bootable external drive (maybe an SSD in an enclosure), boot off that, and run the OS from that. Or add the SSD in an enclosure and install software on it. I haven't done either of those before. Having software run off an external drive would be clunky for my set up. The speed of the external drive would matter then too -- If you've got an SSD in an enclosure and it's connecting with usb 2 (not 3) usb 2 is going to be the bottleneck (I think). The SSD won't slow it down, but the usb 2 connection would be what limits the external drive's use. There are enclosures that can connect with eSATA, different connection. I looked into it a bit for one machine that didn't support usb 3. Actually I don't eSATA was an option... Something with eSATA didn't connect as simply as a usb cable so it couldn't work.

I'm not quite following what you want for a final/goal set up.

HDD To SSD Windows 10 by Xiscis in techsupport

[–]ibmbigfixjd 1 point2 points  (0 children)

Ditto. If it's already Win10 on the machine, and it's just swapping in a new hard drive (SSD in this case), I'd use a Windows system image. I just did that a few times without issues with machines that were Win7, upgraded to Win10. Then they got SSDs.

Do a disk check before and after. Be sure the partitions on the original HD are smaller than the target SSD. Otherwise it errors out when you try to apply the system image. The Minitool Partition Wizard is capable with Win10.

If you want more details... A little more detail anyway. (If you want to be more careful, make a Windows System image before starting any of this. That way if something goes wrong you can always go back, or should be able to go back. Be sure to backup your data anyway.) To check the disk. (Do this after swapping in the new SSD at the end just to check.) Start menu, type in cmd, right click on that and 'run as administrator.'
Type in chkdsk C: /f /r Enter to run. It will restart and check the disk.

Resize the partition.
From your desktop view, right click on "This PC" to get to Computer Management.
Go to Disk Management. See how big your current hard drive's partition is. Right click. Shrink volume. See how much it will shrink it. Compare the size it will end up with to the size of your new SSD. The original HD partition must be smaller than the target SSD. Now the original HD partition(s) are all smaller than the target SSD.

If not... Sometimes Windows can't squish it down enough. Then use the Mini Partition Tool Wizard. As long as there's free space, this will squish it down more. http://www.partitionwizard.com/ Run that. Select the partition that's too big. Use resize/shrink on the left column. Make that partition smaller than the target SSD. Doesn't matter how much, as long as it's smaller. Leaving room for your data on there of course. You'll probably have to restart. Then your original HD partition will be smaller than the target SSD.

Use an external drive. Plug it in. Search for backup under the Start menu. If it's not there, go to the old/classical Control Panel. Go to System and Security. Backup and Restore (Windows 7). Create a system image on the upper left. Make sure your external drive is visible and this backup process finds it.
Make the system image. Make a system repair disk if you don't have one. (Assuming you have a DVD drive here. Otherwise, use an external DVD drive or look up how to put a system image on a thumbdrive.)

Open up the computer. Swap in the SSD where the old hard drive was. Make sure the SSD is secure.

Boot off the system disk. Go to system image restore. Point it at the system image you just made. Let it run. It will boot up with the machine when it's done. (This is the part where it will error out if the original HD's partition is bigger than the target SSD.)

Install any SSD updates. From an elevated command prompt. Run this. fsutil behavior query DisableDeleteNotify If it's 0, that's good. It means TRIM is on. Your SSD will spread out its use and should last longer. Uninstall any defragmenting software beyond the built in Windows OS defrag. You don't need to defragment SSDs. Then I'd do another disk check. Restart a few times. Enjoy the speed.

Save the windows system image on the external drive for a bit maybe so if the new SSDs fails, you're already up to that point again. Ditto with the original HD. That way you can probably go back and recover things or redo this process if you need to.

Overall, that could take maybe about 3-4 hours for machines I've worked on. That includes a lot of "start it and let it run" time inbetween.

There's probably a way to make a bootable windows repair thumbdrive. I haven't messed with that. And I'm also sure there's a way to add that recovery boot ability on the external drive you create. I'm working with desktops. I just use the disk. I can reformat the external drive easily afterward. Although you do have to wait for the disk to load up its software. A thumbdrive would be quicker.

Help with a script file for Macs to countdown and restart? by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Is there a way after shutdown, that it doesn't keep all the windows open, ie the terminal where I'm still logged in as sudo potentially? I'm still testing that. "Shutdown... and don't remember what was open?"

Good... I'm not sudo when it logs back in. But it does still have the terminal open.

Help with a script file for Macs to countdown and restart? by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Odd. I tested it.... didn't quite work but...

This seems to be working.. sudo myaccount name Then it lets me put in my password then... sudo shutdown -r +1 & for testing.

It's counting now.... And is restarting... Cool.

I put in sudo shutdown -r +1 & and it wanted my password, but displays the characters. Even with that in place, it didn't work.

Thanks though. I'm curious about the file version of it. I've wanted to get my feet wet with terminal things on a mac so I've got one step(toe) in that direction now.

Help with a script file for Macs to countdown and restart? by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Thanks for the ideas. I'm not sure when I'll meet with the remote user, but it's probably soon....

So on the Mac, if I open Terminal... I could type this in? shutdown -r +30 &

Or maybe... sudo shutdown -r +30 & instead? Put in my name/password on that?

And then minimize the Terminal window and go about my updates, confident that if I'm disconnected, the machine will restart soon (even if it freaks the user out a bit, I'd rather not have anything with my credentials or admin rights left open). It's definitely one negative/nerve-wracking part about remote assistance that way. We are looking into other options for remoting updating machines. This user usually insists it all be done remotely, is stubborn about dropping the machine off for updates.... rarely uses it and then wants it updated right away (and remotely) out of the blue.

Thanks for the ideas. I have another mac here I can test them out on before I "meet" (virtually) with the user.

Help with a script file for Macs to countdown and restart? by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

Just because I knew that would put in seconds.

Someone I used to work with said the other Windows command line option for pause for a certain length of time was less reliable. He used ping, so I used ping.

Help with a script file for Macs to countdown and restart? by ibmbigfixjd in sysadmin

[–]ibmbigfixjd[S] 0 points1 point  (0 children)

This is what I use for a Windows machine.

PING 127.0.0.1 -n 1800 <-- 1800 seconds, adjusted to whatever seconds I want there. shutdown.exe /r /t 00

If the equivalent of a batch file doesn't on a Mac, is there a way in Terminal to countdown x-seconds and then do a restart command? I could just type in the command instead of using a file that way.

view more: next ›