1 of 1 people found this helpful
From the Terabyte web site--they have a more extensive user guide for ImageW
This is in the list of command line options:/noosn:nThis option controls how the OS is notified of partition changes. It's useful for full drive restores where your source and target drives are the same, but you're sure the restored partitions won't overlap the source (which will be deleted after the restore)./noosn:1 - never send notification to OS about partition changes (a reboot must be used or corruption could occur if existing partitions existed where restored partitions are located). Most users will NOT want to use this option – it's for very advanced users only./noosn:2 – defer the notification until all partitions are restored. This option is safe for all to use.Default if omitted: The OS is notified of partition changes as each partition is restored.
Thanks for the quick response, however the parameter in question was slighly before the /noosn:n switch. I have highlighed the switch that was in question. I'm also on the Terabyte site now looking for a solution too.
REMEXEC32=ldrun h:\Tools\LANDesk\IMAGEW~1\imagew.exe /r /uy /o /d:w0 /nos:200m /nlrm:64 /noosn:2 /f:"""g:\LD0010~1.TBI""" /rb:0
I found the answer on what that switch does in terabyte documentation.
This option offers a way to prevent scaling of small partitions when scaling to a larger drive. Partitions that are size (in bytes) or smaller will not be scaled. For example:
200m would not scale partitions that are 200MiB or smaller. Note that the .ini file value is not used on command-line based operations.
Default if omitted: All partitions are scaled when scaling
Looks like I do not need that command...
Thanks for your help,
Sorry, copied the wrong one. Looks like you found what you needed.
I just wanted to update everyone on this post, in case someone else out there did the same thing I did...
When I started setting up all of the OSD stuff on our new landesk 9 server, I stripped out the old folder structure I had on our 8.8 server which included imagew 2.0. The only problem was that the imagew 2 from 8.8 is an older version that does not support the new switches provided by LD 9. Once I realized this, and replaced the imagew.exe with the proper version it cleared up this issue.