Hi Guys

I have just taken stock of some new optiplex 790 for my Windows 7 roll out.
I use a scripted install and have being pushing down Windows 7 from K2000 to other optiplex models and latitudes without any probs at all.
I script the 790 and it runs all the way through and finishes installing windows 7.
When I log on and get the message balloning from the notification area nee: system tray

Failed to connect to a windows service
Windows could not connect to the System Event
Notification Service service. This problem prevents
standard users from logging on to the system.
As an administrative user, you can review the System
Event Log for details about why the service didn't

This happens only (so far ) on the 790 in my envrionment.
It doesnt happen on every log on .
It does happen if I log in with a domain admin account , local admin account or domain user account.
I did a search and people who have been getting this message seem to have Vista , and have their pcs running for a while.
This is on a brand new imaged pc. I literally just finished scripting this pc 20 mins ago.
Odd one.....but I cant roll out Windows 7 if Im getting unexplained messages popping up.
The service (System Event Notification) has not been altered by me , or any application that I know off.
Is it set to start automatically , and when I check the service it is running , as are its dependencies.
I can restart the service without any errors.
The first time this occured (last Thursday) I put it down to a bad image or some sort of corruption.
But Ive built 4 different optiplex 790s
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


So you are pushing down windows 7 Scripted Install?

Make sure the only driver for this os for this computer is network.

If using the driverfeed workaround method, make sure you are using the latest version ( I believe).

Just push a scripted install first, see if the problem exists, then add on your postinstallations.
Answered 12/06/2011 by: cserrins
Red Belt

Please log in to comment