Registered member login:
Register Now
Altirigos » Homepage2

» Current Poll
Vista?
Staying on XP until Windows 7 - 71.74%
99 Votes
Already on Vista - 10.87%
15 Votes
Planning an upgrade to Vista soon - 10.14%
14 Votes
Other (please explain) - 7.25%
10 Votes
Total Votes: 138
You may not vote on this poll.
» Stats
Members: 6,826
Threads: 9,759
Posts: 47,766
Top Poster: Nick (4,800)
Welcome our newest member, Burken
» Online Users: 18
1 members and 17 guests
Burken
Most users online at once 294, 06-30-2007 at 01:24 PM.
» January 2009
S M T W T F S
28293031 1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
View Single Post
Old 08-21-2008, 06:34 PM   #6 (permalink)
Dovik
 
Status: Junior Altiris Admin
Join Date: 08-17-2008
Location: Florida
Posts: 9


Solved

I was able to get this problem resolved today and thought I would post the resolution in case it may be useful to someone else in the future.
The problem turned out to be the PXE.ini file not being updated correctly, however I suspect the actual root cause was the PXE Config Helper Service.
When comparing the contents of the PXE.ini against what was appearing on the client, one of the values was missing entirely yet appearing on the client, and the order in which the boot options were to be presented to the user appeared differently on the client than how they were configured in the .ini file.
I deleted everything in the PXE.ini file except for the first three rows, then restarted the PXC Config Helper Service. Actuall, when I tried to restart the Service the process hung, and then I just pressed the Start button on the toolbar and it fired right up.
After that, I rebooted a client machine and now see the current boot menu options.
Cheers!
Dov
Dovik is offline  
 
Powered by vBadvanced CMPS v3.0 RC2

All times are GMT -4. The time now is 03:05 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
vB.Sponsors
Altirigos