How to install Deployment Server on Microsoft Cluster Server.
Article #: AKB7197
Author: 3108
Date: 3/11/2005 9:19:28 AM
--------------------------------------------------------------------------------
Question:
How to install Deployment Server on Microsoft Cluster Server?
Answer:
1. There must be two servers clustered and working.
2. Install the enterprise version of SQL from the primary node onto the virtual server. SQL will not let you install onto the virtual server that Microsoft Cluster Service created so you have to make a new virtual server. To run the Deployment Server (DS) on a cluster, a cluster virtual IP needs to be established.
3. Install the DS with the same settings from each cluster node but use the cluster IP address anywhere you enter an IP. From the Primary node in the cluster (the node that owns the storage) install an instance of the DS using the shared storage for the DS database and the Client Access Files. The DS should be installed to the local drive.
4. Fail the cluster over to the Secondary node and do the install the exact same way.
5. With all the files pointing to the exact same location, install the DS to the local drive. When both machines are rebooted, they should both be running the Altiris Express Service in Services Manager.
7. Now open Cluster Manager and create a new Generic Service; name the service the same name as the one running in Services Manager. Make it part of the Cluster Group that all the other services are running in.
8. Now it should be possible to fail over the service and it should start the Altiris Express Service on the inactive node.
Because the DS is not cluster aware, anytime there is an active node transfer it will be as if the axengine died and restarted. That means Aclient will probably become orphaned until it attempts a reconnect.
22 June 2005
Windows Installer Exit codes
Here, you can find al lot of exit codes for Windows Installer : Windows Exit codes
14 June 2005
06 June 2005
Activate the Diagnostics without showing the NSCLient Icon
'vbscript
dim client
set client = CreateObject ( "Altiris.AeXClient" )
dim sessmgr
set sessmgr = client.SessionManager
'Client Diagnostics
sessmgr.ActivateObject ( "{E8B8B9D4-A461-4E19-9F14-B72E5110F631}" )
'Network Diagnostics
sessmgr.ActivateObject ( "{1D588FDC-D1DA-40DD-99F7-D43D161F043E}" )
'Power Management
sessmgr.ActivateObject ( "{2C71C589-25C8-4D5B-8FD2-68B376566601}" )
dim client
set client = CreateObject ( "Altiris.AeXClient" )
dim sessmgr
set sessmgr = client.SessionManager
'Client Diagnostics
sessmgr.ActivateObject ( "{E8B8B9D4-A461-4E19-9F14-B72E5110F631}" )
'Network Diagnostics
sessmgr.ActivateObject ( "{1D588FDC-D1DA-40DD-99F7-D43D161F043E}" )
'Power Management
sessmgr.ActivateObject ( "{2C71C589-25C8-4D5B-8FD2-68B376566601}" )
05 June 2005
Ports and Protocls
Want to find out more about the ports and protocols for DS 6.X?
Check out this Altiris White Paper AKB5447
03 June 2005
Batch file which will reconnect inactive Deployment Agent for Windows
KB Article : AKB5705
Question:
Sometimes administrators are not sure why aclient machines are not connected to the deployment server. Often times this is because the user has shut down the service. What can an administrator do?
Answer:
Run this Sql Query on against the database:
This batch file will need to be modified to stop and then start the service to reconnect the clients that think they are connected but are not actually connected.
Note: this must be run as a domain administrator to allow proper authentication to restart the aclient service.
Also note the OSQL statement may need to be modified if a remote SQL server exits or use SQL authentication to access the express database.
Example Batch file:
rem This will query the eXpress database for computers that are not connected and for each one will attempt to connect to the computer and start the aclient service.
for /f %%i in ('osql -E -d eXpress -h-1 -Q "set nocount on;select name from computer where computer_id not in (select computer_id from sessions)"') do sc \\%%i start aclient
This batch file will need to be modified to stop and then start the service to reconnect the clients that think they are connected but are not actually connected.
Note: this must be run as a domain administrator to allow proper authentication to restart the aclient service.
Also note the OSQL statement may need to be modified if a remote SQL server exits or use SQL authentication to access the express database.
Example Batch file:
rem This will query the eXpress database for computers that are not connected and for each one will attempt to connect to the computer and start the aclient service.
for /f %%i in ('osql -E -d eXpress -h-1 -Q "set nocount on;select name from computer where computer_id not in (select computer_id from sessions)"') do sc \\%%i start aclient
Change IP Address for PXE
In this White Paper you can find the way to change the IP Address for a PXE Server.
Or try this:
Change Altiris Deployment/PXE IP adress.
Stop All Altiris DS services.
Change IP i these Files:
C:\Program Files\Altiris\eXpress\Deployment Server\default.cfg
C:\Program Files\Altiris\eXpress\Deployment Server\PXE\PXE.ini
C:\Program Files\Altiris\eXpress\Deployment Server\aclient.inp
and the %name%\%name%.bdc Files under
C:\Program Files\Altiris\eXpress\Deployment Server\Bootwiz\config\
Start Altiris DS Services.
Change Bootdisks IP
Start DS Console (Not Webconsole)
Open PXE Configurator
Mark The Bootdisk you want to change
Select Make Boot Files
Change The line (set CONIP=-ip192.168.0.1) in autoexec.bat and startnet.bat
Right click on Th Bootdisk an select Make Boot File
Close and Repeat For all Bootdisks
Just an add-on to this excellent article.As I installed PXE Server after changing IP, there were no \PXE\PXE.INI to change in, and the PXE Server Service refused to start after the installation. I sorted it out by changing adress in \PXE\RPC.ini as well. Then PXE.ini gets created automatically, and the service started as it should.
20 May 2005
Subscribe to:
Posts (Atom)