Hi
A strange question for all admins/desktop support guys...
We are currenlty starting to roll out a new PCI compliant image (XP Pro Default build with updates, Java 6 and Callmedia pre loaded).
So far the main image is fine, however, one campaign requires an old IBM App that is a pain to install, so we created an MSI install for it... again, so far so good... the MSI is pushed out via a GPO from AD... and installs fine...
The problem is this, Note: the PC's work fine Until you install the MSI...
At the login screen, press CTRL-ATL-DEL, enter login details and press enter... then you get a blank screen with just a mouse cursor.... and nothing happens, Until you press CTRL-ALT-DEL... the the profile will suddenly load, this affects ALL users on the machine, local profiles, roaming profiles and new accounts... even the local admin account...
I have tried to Google it, but cannot find any account of such an issue, any of you come accross this before?
We have had the odd PC with this fault before, but very rare, were as we can be sure the msi install is causing this issue on this new build.
A strange question for all admins/desktop support guys...
We are currenlty starting to roll out a new PCI compliant image (XP Pro Default build with updates, Java 6 and Callmedia pre loaded).
So far the main image is fine, however, one campaign requires an old IBM App that is a pain to install, so we created an MSI install for it... again, so far so good... the MSI is pushed out via a GPO from AD... and installs fine...
The problem is this, Note: the PC's work fine Until you install the MSI...
At the login screen, press CTRL-ATL-DEL, enter login details and press enter... then you get a blank screen with just a mouse cursor.... and nothing happens, Until you press CTRL-ALT-DEL... the the profile will suddenly load, this affects ALL users on the machine, local profiles, roaming profiles and new accounts... even the local admin account...
I have tried to Google it, but cannot find any account of such an issue, any of you come accross this before?
We have had the odd PC with this fault before, but very rare, were as we can be sure the msi install is causing this issue on this new build.