Tuesday, March 23, 2004
Monday, March 15, 2004
Monday, March 08, 2004
Hot fix A for DS 6.0 has been released.: "RE: Hot fix A for DS 6.0 has been re...
Here is a list of fixes so that you dont have to download the file to see them and that they show up on forum searches properly.
6.0 Hotfix A fix list:
1. Rdeploy.exe more intelligently handles images that are spanned to multiple CDs. MakeImx.exe has been added to TechSup folder
2. Rdeploy.exe run manually now saves the post config data
3. 'Does not contain' filter is now working on job conditions.
4. Auto Logon set by PC Transplant no longer removed by Aclient.exe
5. Client multicast connectivity issues have been corrected.
6. Intel 1000mt adapter is now configured properly in oemsetup.inf
7. NICList.dat & PCIDetect have been modified to handle Broadcom nics properly
8. DS Filter value length has increased.
9. Rdeploy.exe now handles hard drives larger than 128 GB
10.Script now pulls descriptions properly and no longer gives the error 'Please enter no more than 128 characters'
11.Makeimx.exe has been added to TechSup folder. Makeimx.exe will create an index file (.imx) for a split image file. All the split image files for an image need to be in the same folder to run makeimx.exe, for example: makeimx
The .imx file and the first split file of the image need to stay together. This will eliminate extra disk swapping when the image is restored.
A DOS, Linux, and Windows version of Makeimx is in the \TechSup folder.
12.Deployment Agent for Windows (AClient) no longer gives 'No license slots available' on upgrade from 5.6 to 6.0 in certain instances.
13.We now handle NetX thin"
Here is a list of fixes so that you dont have to download the file to see them and that they show up on forum searches properly.
6.0 Hotfix A fix list:
1. Rdeploy.exe more intelligently handles images that are spanned to multiple CDs. MakeImx.exe has been added to TechSup folder
2. Rdeploy.exe run manually now saves the post config data
3. 'Does not contain' filter is now working on job conditions.
4. Auto Logon set by PC Transplant no longer removed by Aclient.exe
5. Client multicast connectivity issues have been corrected.
6. Intel 1000mt adapter is now configured properly in oemsetup.inf
7. NICList.dat & PCIDetect have been modified to handle Broadcom nics properly
8. DS Filter value length has increased.
9. Rdeploy.exe now handles hard drives larger than 128 GB
10.Script now pulls descriptions properly and no longer gives the error 'Please enter no more than 128 characters'
11.Makeimx.exe has been added to TechSup folder. Makeimx.exe will create an index file (.imx) for a split image file. All the split image files for an image need to be in the same folder to run makeimx.exe, for example: makeimx
The .imx file and the first split file of the image need to stay together. This will eliminate extra disk swapping when the image is restored.
A DOS, Linux, and Windows version of Makeimx is in the \TechSup folder.
12.Deployment Agent for Windows (AClient) no longer gives 'No license slots available' on upgrade from 5.6 to 6.0 in certain instances.
13.We now handle NetX thin"
Friday, March 05, 2004
Thursday, March 04, 2004
Wednesday, March 03, 2004
Topic: Altiris WOL on DELL optiplex
http://www.altirisguru.com/forum/forum_posts.asp?TID=885&PN=1
romeowang
Newbie
Joined: Sep 06 2003
Posts: 3 Posted: Oct 21 2003 at 11:33am | IP Logged
--------------------------------------------------------------------------------
Since i don't know what kind of computer and Nic. you going to have to find this yourself.
Most of the Optiplex has a 3Com Nic onboard. you need to go to www.3com.com to get the Nic finder to find out what kind of nic it is. and then download the right updater Tool named "windiags.exe". And run it on the computer which you need to enable WOL. You don't need to config anything, just run the file. then you can get rid of the file.
this is how I fixed my OptiPlex GX110 WOL problem. Use as your own risk.
Hope this will help.
~Romeo
Back to Top
cnpalmer
Newbie
Joined: June 25 2003
Location: United States
Posts: 28 Posted: Oct 27 2003 at 2:24pm | IP Logged
--------------------------------------------------------------------------------
You will need to make sure WOL is enabled in the BIOS. Almost all Dell PC's from the GX line on up have this option. You may have to do a BIOS upgrade on older models to enable this.
The utlitiy described will turn the WOL option on in the BIOS but the client will need to be rebooted for it to take affect.
In order for WOL to work thru DS you will need to designate one of the clients running AClient as a WOL Proxy. You can do this thru the client properties page in DS. This client will listen for the WOL signal from the DS and then send it to the respective PC. There is no way around this. The power control pfeatures in DS are not very customisable. The downside to this is that you must make sure your client designated as the proxy is ALWAYS ON!
My assumtion here is that you do not have a client designated as a WOL Proxy. therefore the WOL request from DS is not being heard.
This should help. Just be aware that you will need to desingate a WOL Proxy client on EACH subnet.
__________________
Benjamin Palmer
PC Tech Support Specialist
Network Services
Information Systems
Baystate Health System
Work: (413)794.5283
Pager: (413)261.4695
Back to Top
romeowang
Newbie
Joined: Sep 06 2003
Posts: 3 Posted: Oct 27 2003 at 3:28pm | IP Logged
--------------------------------------------------------------------------------
WOL Proxy is only used when you have subnets on your network, let's say you have your DS server and your Clients in different subnets. Otherwise you don't need WOL Proxy Client.
~Romeo
Back to Top
pera
Newbie
Joined: Oct 10 2003
Location: Sweden
Posts: 1 Posted: Nov 05 2003 at 4:37am | IP Logged
--------------------------------------------------------------------------------
CHANGE PROPERTIES ON THE NIC IN CONTROL PANEL: POWER CONTROL: WAKE ON LAN
"Allow this device to bring the computer from the standby"
Back to Top
http://www.altirisguru.com/forum/forum_posts.asp?TID=885&PN=1
romeowang
Newbie
Joined: Sep 06 2003
Posts: 3 Posted: Oct 21 2003 at 11:33am | IP Logged
--------------------------------------------------------------------------------
Since i don't know what kind of computer and Nic. you going to have to find this yourself.
Most of the Optiplex has a 3Com Nic onboard. you need to go to www.3com.com to get the Nic finder to find out what kind of nic it is. and then download the right updater Tool named "windiags.exe". And run it on the computer which you need to enable WOL. You don't need to config anything, just run the file. then you can get rid of the file.
this is how I fixed my OptiPlex GX110 WOL problem. Use as your own risk.
Hope this will help.
~Romeo
Back to Top
cnpalmer
Newbie
Joined: June 25 2003
Location: United States
Posts: 28 Posted: Oct 27 2003 at 2:24pm | IP Logged
--------------------------------------------------------------------------------
You will need to make sure WOL is enabled in the BIOS. Almost all Dell PC's from the GX line on up have this option. You may have to do a BIOS upgrade on older models to enable this.
The utlitiy described will turn the WOL option on in the BIOS but the client will need to be rebooted for it to take affect.
In order for WOL to work thru DS you will need to designate one of the clients running AClient as a WOL Proxy. You can do this thru the client properties page in DS. This client will listen for the WOL signal from the DS and then send it to the respective PC. There is no way around this. The power control pfeatures in DS are not very customisable. The downside to this is that you must make sure your client designated as the proxy is ALWAYS ON!
My assumtion here is that you do not have a client designated as a WOL Proxy. therefore the WOL request from DS is not being heard.
This should help. Just be aware that you will need to desingate a WOL Proxy client on EACH subnet.
__________________
Benjamin Palmer
PC Tech Support Specialist
Network Services
Information Systems
Baystate Health System
Work: (413)794.5283
Pager: (413)261.4695
Back to Top
romeowang
Newbie
Joined: Sep 06 2003
Posts: 3 Posted: Oct 27 2003 at 3:28pm | IP Logged
--------------------------------------------------------------------------------
WOL Proxy is only used when you have subnets on your network, let's say you have your DS server and your Clients in different subnets. Otherwise you don't need WOL Proxy Client.
~Romeo
Back to Top
pera
Newbie
Joined: Oct 10 2003
Location: Sweden
Posts: 1 Posted: Nov 05 2003 at 4:37am | IP Logged
--------------------------------------------------------------------------------
CHANGE PROPERTIES ON THE NIC IN CONTROL PANEL: POWER CONTROL: WAKE ON LAN
"Allow this device to bring the computer from the standby"
Back to Top