Registered member login:
Register Now
Altirigos » Homepage2

» Current Poll
Do you leave the Aclient enabled?
YES - 82.31%
107 Votes
NO - 17.69%
23 Votes
Total Votes: 130
You may not vote on this poll.
» Stats
Members: 9,492
Threads: 11,748
Posts: 55,283
Top Poster: Nick (4,981)
Welcome our newest member, stavchan
» Online Users: 50
0 members and 50 guests
No Members online
Most users online at once 294, 06-30-2007 at 12:24 PM.
» March 2010
S M T W T F S
28 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 123
Thread: Problems Ahoy!
View Single Post
Old 06-13-2007, 09:54 AM   #1 (permalink)
cbrunet
 
cbrunet's Avatar
 
Status: Junior Altiris Admin
Join Date: 06-13-2007
Location: Pembroke, Ontario, Canada
Age: 26
Posts: 11


Unhappy Problems Ahoy!

Greetings Experts, We just recently purchased an Altiris solution, and I am slowly trying to wrap my head around its capabilities. I thought I had most of it down, but now I just can't seem to get anything working. Here a few examples of this going awry.

1st: Image Creation Problems The first problem we are having is that I can't seem to image a PC. I've tried "New Computer" (NC) systems to no avail. The NC will load up the WinPE, and then go straight to "Session Terminated" and will reboot itself. The deployment server will still list it as "Restarting computer to prepare for imaging..." but will never let it go any farther in the PE. Whern it does reboot and goes to the PXE menu, it wants to boot the next BIOS device, and if I don't tell it otherwise, will boot into whatever OS is isntalled. Any system with a full AClient installed on it will work, I just need to be at the terminal to send it to the PE.

2nd: Scripts and Jobs I've been trying to update my systems so that they can be remotely controlled (that's issue nuber 3). During initial deployment of the Altiris Client, I never thought to have the line set to check "Allow this computer to be remotely controlled". I know, kinda silly, but whatever. So I changed the INP file to include this, and just figured I would rerun my batch file (aclient.exe aclient.inp -install) and I'd be fine, but oh wait, theres a fancy "run script" thing in DS, cool, lets do that. So the script will just run, and run, and run and run. You will see the Aclient in the system tray opening, connecting, and closing. If you open it up, you see it connecting to the server, then it runs some script, and then it exits. Is this just not cool to do it this way and I'm confusing the hell out of it? Is there an easier way to mass-ly get this setting checked?

3rd: Remote Control I tried remote control yesterday. It worked, it worked great in fact, that is what pushed me to get the script going today. So, I was going to show someone it, and of course, it just wouldn't work. I can't figure out what is different, the system I am remote connecting to is the same (except now its a different user, but same rights to the local pc). It will just sit at "Waiting for clients to accept connection", and then it errors out. I think that's everything so far.

Needless to say I'm getting frustrated. Any ideas gents?
cbrunet is offline   Reply With Quote
 
Powered by vBadvanced CMPS v3.0 RC2

All times are GMT -4. The time now is 11:57 AM.


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