Deployment Solution

 View Only
  • 1.  Managing Wireless Clients with DS 6.9 SP3

    Posted May 04, 2012 04:44 PM

    I just took on a job as a system admin and have not had a chance to really get familiar with Altiris and I have zero previous experience with it. The previous sys admin moved to a different position within our company and will train me up on Altiris when he gets back from training in 2 weeks.

    One of our Help Desk technicians (he uses Alritis, but does not manage it) came to me and said that he's not able to connect to the computers he is managing when they are connected wirelessly. He has to push out a batch of computers before I get to sit down with the previous sys admin and go over all of the details of managing the DS server.

    Can you point me to some user manuals, guides, or give me some pointers on making clients visible to the server when they are connected wirelessly?

    I would think it shouldn't be any different than a hard-wired connection, but the help desk tech said that he has not been able to communicate with any of his test systems.

    Thanks again for any help. I know it is a very open-ended question.



  • 2.  RE: Managing Wireless Clients with DS 6.9 SP3

    Posted May 04, 2012 05:12 PM

    Is there a special wireless agent we need to install by any chance?

    The wireless devices are on the same subnet as our wired devices. We are able to see the wired, but not the wireless devices.

    Thanks again.



  • 3.  RE: Managing Wireless Clients with DS 6.9 SP3

    Posted May 04, 2012 11:46 PM

    I would first check if a firewall may block some Ports on the wireless nic for some security reasons...

    Altiris Products Ports and Protocols:

    http://www.symantec.com/connect/sites/default/files/Altiris%20Products%20Ports%20and%20Protocols.pdf

     

    Regards,

    tester2k5



  • 4.  RE: Managing Wireless Clients with DS 6.9 SP3

    Posted May 15, 2012 10:40 AM

    Or has it always been a problem? Altiris doesn't distinguish b/w wired/wireless connections, but it does require the aclient or dagent to be installed and configured properly on every client. This is an exe/service that communicates with the deployment server and passes the commands to the client. Settings for aclient/dagent can be centrally set so that little configuration is needed, but if the aclient/dagent is not installed on the laptops then it will have to be added to the image (or manually installed on each one).  

    Since they are already in production, i would assume they were previously imaged and managed by the deployment server via hardwire.   have they ever been seen wirelessly by the DS? if you plug one in wired does it show up? if you run a PXE server in conjunction with altiris, does it see PXE and does altiris give you boot options? You may have to hit F8 if the laptop doesnt have any pre-boot environment jobs pending, but it should still connect, see no pending jobs, and then continue with the next default boot option (ie hard drive).