Ghost Solution Suite

 View Only
  • 1.  Windows 10 deployed via Symantec Ghost 3.0 HF4 - Support for Dual Display Orientation

    Posted Jan 07, 2016 08:22 PM

    Hello,
    I'm working on setting up a classroom environment, in which all of the machines are deployed via Ghost/Altiris 3.0 HF4 with Windows 10.
    My images deploy flawlessly, with 1 exception. We are using dual monitors; 1 monitor in Landscape, the other in Portrait. On the source machine, the displays are configured properly, however, when I snap the image, and then redeploy it, the orientation is set to landscape on all of the target machines.

    These machines are all identical hardware, identical monitors, and all the drivers are up to date. I even went as far as resetting the monitors settings, and trying the config from within the ATI Control Center, and it still drops the monitor orientation.

    Can anyone direct me on if there is a way to set this orientation, so that I don't need to reset it by hand after the image is deployed everytime? I'd like to be able to do this natively if possible. Is there a regkey I can set? I'm not opposed to installing a magical piece of software to do it, but if I can accomplish this without installing something, that would be preferred.

    Thank you all for your help!

    Chris



  • 2.  RE: Windows 10 deployed via Symantec Ghost 3.0 HF4 - Support for Dual Display Orientation

    Posted Jan 11, 2016 10:45 AM

    To anyone else having this issue.

    I had researched just using a hotkey within the ATI management suite, however, found this would not work, as its dependent on which monitor the cursor is active on.

    I found a little tool, which doesn't require installation or admin access.

    The tool is called display. (http://noeld.com/programs.asp#Display).

    I placed this tool in my tools folder, and simply ran

    C:\display.exe /device 2 /rotate 90



  • 3.  RE: Windows 10 deployed via Symantec Ghost 3.0 HF4 - Support for Dual Display Orientation

    Posted Jan 20, 2016 09:08 AM

    Chances are that the information is stored in the current user profile and would be lost during sysprep unless you identify the exact setting and make sure it is in the .default user profile. Your solution is clearly working, but in general, any non-default settings that a user can make are almost always stored in the user profile.