How old is your KVM? My 4 port had to be replaced once we really started rolling out win7 as it would behave quite erratically. Even now my kvm has the occasional issue with usb mice not working through it but plugged directly in the pc it works fine.
Thank You, Roger Truss [email protected] h (920) 456-8302 c (920) 203-0625 On Thu, Jul 10, 2014 at 9:02 PM, Harry Mavromatidis <[email protected]> wrote: > In MDT under the default heading set these to the resolution desired: > > > > [Default] > > XResolution=1280 > > YResolution=1024 > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of * > [email protected] > *Sent:* Wednesday, July 9, 2014 9:45 PM > > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Setting Screen Resolution for the WinPE Session > > > > Newer WinPE will set the native resolution of the display. (IIRC v4.0 and > newer) > > > ------------------------------ > > *From:* [email protected] [[email protected]] > on behalf of Keith Garner (Hotmail) [[email protected]] > *Sent:* Wednesday, July 09, 2014 7:39 PM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Setting Screen Resolution for the WinPE Session > > Stream of consciousness questions… J: > > > > Not clear to me **where/when** this is happening… On which machines > (uefi? Make/Model), and what the problem scenario is. > > Is this happening during WDS boot menu selection? During the Kernel > loader? Or when WinPE has fully started? > > MDT and OSD both put their dialogs at the center of the screen, so that > can’t be the problem. > > Does the problem go away if you connect to a CRT (not flat panel) monitor, > Yes, I know it’s 2014, but still… > > Or are you talking about the sync range of the monitor? Specifically what > resolution is it running at? (Typically monitors will say what the > offending resolution refresh rate is). > > BY default in MDT, the unattend.xml file is set to 1024 x 768 x 32bits x > 60Hz: C:\Program Files\Microsoft Deployment > Toolkit\Templates\Unattend_PE_x64.xml > > > > Your machine could also have driver problems and/or a BSOD, I once had a > problem with some uEFI Intel Prototype motherboards where the screen would > go black, the symptoms appeared to be just like a BSOD, however the machine > wouldn’t reboot. The only way I knew for sure that the machine was still > working was that I had to type blind into my WinPE image: F8 à wpeutil > shutdown when the machine actually shutdown, I was able to rule out BSOD, > and I could work on other scenarios. It turned out that the display driver > was just not working, and **NOTHING** was getting sent to the display > driver, it was **not** a refresh issue, but a uEFI firmware issue. > > > > -k > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *steven hosking > *Sent:* Wednesday, July 9, 2014 2:26 PM > *To:* [email protected] > *Subject:* [MDT-OSD] Setting Screen Resolution for the WinPE Session > > > > Hi Guys, > > > > we have an odd one where when building the new computers from PxE or media > the screen we have attach goes out of range (Yes yes before you ask we have > change the screen out, but still having the issue as a result of the KVM we > think) and then blank so if our guys aren’t quick enough selecting the TS > they want to build with they have to restart the screen, it’s a mild > annoyance but just wondering if there is a way to define the Resolution for > the WinPE at the initial boot time where you get prompted for the password > and to select the TS? > > > > any advice would be great. > > > > Cheers > > > > Steve >
