28 November 2007
best practice to enabling WOL proxies using Deployment Server 6.x?
For each broadcast domain that cannot receive Wake-on-LAN (WOL) packets from the Deployment Server, designate one always-on computer to work as the WOL proxy. The WOL proxies must be configured to use TCP/IP to connect to a Deployment Server.In Deployment Server 6.1, one WOL proxy can exist per broadcast domain.
In Deployment Server 6.5, it is possible to enable multiple WOL proxies per broadcast domain because Deployment Server has the ability to dynamically select one WOL proxy per broadcast domain for use.
In Deployment Server 6.5, it is possible to enable multiple WOL proxies per broadcast domain because Deployment Server has the ability to dynamically select one WOL proxy per broadcast domain for use.
PXE-E53 error in Deployment Solution 6.8 SP2 with Initial Deploy disabled
In Deployment Solution 6.8 SP2, if Initial Deployment is disabled, the PXE client will display the error "PXE-E53 No boot filename received".
Cause
Prior to Deployment Solution 6.8 SP2, a PXE Client who is not in the Deployment Server's database would get the default PXE boot menu, using the default countdown before booting to the next device. The PXE Server in Deployment Solution 6.8 SP2 is not acting this way; instead, it does not respond to PXE Client requests if the computer is not already in the database when Initial Deploy is disabled.
________________________________
Resolution
To obtain the same reaction of a pre-6.8 SP2 PXE Server, enable Initial Deploy, set the Initial Deploy Boot Option to (None), and the timeout to the desired value.
To do this:
1. Open the Deployment Console.
2. From the Deployment Console open the PXE Configuration Utility (Tools > PXE Configuration).
3. In the PXE Configuration Utility, change to the DS tab.
4. On the DS tab, uncheck Disable Initial Deploy.
5. Change the radio button to the desired timeout option.
27 November 2007
Online activation workshop for Intel vPro using Altiris Client Management Suite
All you need to know about vPro Activation with Altiris
26 November 2007
Difference between Domain Browse List and Domain Membership
Domain Browse List and Domain Membership
You can choose to discover all computers currently sharing files or printers running the Messenger service (Domain Browse List), and/or all computers that have trust accounts in the domain (Domain Membership).
The available discovery methods are Domain Browse List and Domain Membership. These settings are used for asynchronous (click Discover Now) and scheduled discovery. Select at least one method.
Domain Browse List —This option discovers all computers (including Windows 95, 98, 98 SE and ME computers) that are sharing files or printers or are running the Messenger service.
Domain Membership —This option discovers all computers with trust accounts in the domain. This finds all Windows NT/2000/XP/2003 computers in the domain. However, it will not find any Windows 95, 98, 98 SE and ME computers.
Note: This method is substantially slower than the Domain Browse List method and will not identify the computer’s operating system.
Domain Browse List
The Domain Browse List works by enumerating the records in the computer browse list. This computer browse list was designed for a small, peer-to-peer environment, so it does not scale to large environments well.
When the Notification Server performs a Domain Browse List discovery, it requests a copy of the computer browse list, which includes additional information such as the computer’s operating system and version. It then does a reverse lookup of the computer’s name to get its IP address.
You might have problems discovering computers using this method if:
The computer is not in the computer browse list.
The computer is in the computer browse list but not registered as sharing files.
It can take between 15 and 51 minutes for changes to be reflected in the computer browse list.
Note: The Domain Browse List discovery method gets as much of the computer browse list as it can as fast as it can. This can overload a PDC in a large domain or a multi-domain environment. We recommend you run this outside business hours, preferably over a weekend.
Domain Membership
This works by enumerating the computer accounts in the specified domains.
When you add a Windows NT/2000/XP/2003 computer to a domain, a computer account is created in that domain. This computer account is used by the computer to authenticate with the domain so the computer can authenticate user logons using a secure connection. Windows 9x computers do not create a computer account, which is why you cannot find Windows 9x computers using this method.
When discovering computers using the Domain Membership method, Notification Server catalogs these accounts. Unlike the Domain Browse List method, these accounts have no additional information beyond the computer’s name. Notification Server still does a reverse lookup on the name to get its IP address.
If problems occur using this discovery method, check that accounts exist for these computers using Server Manager (Windows NT 4.0) or Active Directory Users and Computers (Windows 2000 and later).
Both of these methods write errors to the Notification Server log file. If you ever have a problem regarding Resource Discovery, check these log files for information.
You can choose to discover all computers currently sharing files or printers running the Messenger service (Domain Browse List), and/or all computers that have trust accounts in the domain (Domain Membership).
The available discovery methods are Domain Browse List and Domain Membership. These settings are used for asynchronous (click Discover Now) and scheduled discovery. Select at least one method.
Domain Browse List —This option discovers all computers (including Windows 95, 98, 98 SE and ME computers) that are sharing files or printers or are running the Messenger service.
Domain Membership —This option discovers all computers with trust accounts in the domain. This finds all Windows NT/2000/XP/2003 computers in the domain. However, it will not find any Windows 95, 98, 98 SE and ME computers.
Note: This method is substantially slower than the Domain Browse List method and will not identify the computer’s operating system.
Domain Browse List
The Domain Browse List works by enumerating the records in the computer browse list. This computer browse list was designed for a small, peer-to-peer environment, so it does not scale to large environments well.
When the Notification Server performs a Domain Browse List discovery, it requests a copy of the computer browse list, which includes additional information such as the computer’s operating system and version. It then does a reverse lookup of the computer’s name to get its IP address.
You might have problems discovering computers using this method if:
The computer is not in the computer browse list.
The computer is in the computer browse list but not registered as sharing files.
It can take between 15 and 51 minutes for changes to be reflected in the computer browse list.
Note: The Domain Browse List discovery method gets as much of the computer browse list as it can as fast as it can. This can overload a PDC in a large domain or a multi-domain environment. We recommend you run this outside business hours, preferably over a weekend.
Domain Membership
This works by enumerating the computer accounts in the specified domains.
When you add a Windows NT/2000/XP/2003 computer to a domain, a computer account is created in that domain. This computer account is used by the computer to authenticate with the domain so the computer can authenticate user logons using a secure connection. Windows 9x computers do not create a computer account, which is why you cannot find Windows 9x computers using this method.
When discovering computers using the Domain Membership method, Notification Server catalogs these accounts. Unlike the Domain Browse List method, these accounts have no additional information beyond the computer’s name. Notification Server still does a reverse lookup on the name to get its IP address.
If problems occur using this discovery method, check that accounts exist for these computers using Server Manager (Windows NT 4.0) or Active Directory Users and Computers (Windows 2000 and later).
Both of these methods write errors to the Notification Server log file. If you ever have a problem regarding Resource Discovery, check these log files for information.
Release Notes for Deployment Server 6.9 (Beta)
Windows Server 2008 Support
Deployment Solution 6.9 provides imaging and management support for Windows
Server 2008.
Agent support is provided using DAgent (first introduced on Windows Vista). DAgent
is fully functional on Windows Server 2008 and supports a full range of agent
functionality. DAgent runs on Win32, Win64 and IA64 Itanium platforms.
RDeploy, ImageX, and Ghost Imaging of Windows Server 2008
Deployment Solution 6.9 provides the ability to capture and deploy Windows Server
2008 images using RDeploy, ImageX, and Ghost using WinPE 2.1. ImageX and Ghost
support Win32 and Win64 platforms in WinPE 2.1.
RDeploy and Image X also provide Windows Server 2008 imaging support on
Itanium platforms, and RDeploy provides support for imaging from Linux automation.
Windows Server 2008 Scripted OS Install Job
Scripted server installations are supported for Windows Server 2008.
WinPE 2.1 Support (see below)
Deployment Solution 6.9 supports WinPE 2.1 for pre-boot and imaging tasks. Older
versions of WinPE are not supported.
Remote Agent install for Deployment Agent
Deployment Solution 6.9 introduces Remote agent install for Vista and Windows
Server 2008.
Support Views based on permission of Group
Deployment Solution 6.9 can restrict viewing of computers from unauthorized users,
based on their rights to manage a given computer. When a user without access
rights to a computer or group of computers logs in, those computers are not visible.
This is option is disabled by default.
VMWare Virtual Center 2.01 support
In the Deployment Console, you can add or import 1.x and 2.x virtual centers. These
virtual centers are displayed in a tree view as Rack and Blade enclosures do with a
visual relationship between the virtual center and the virtual machines that it hosts.
Administrators can visually distinguish a virtual center 1.x from a virtual center 2.x.
Scripted installations of VMWare ESX 3
Deployment Solution 6.9 provides support for scripted installations of VMWare ESX
Red Hat Enterprise Linux 5-update 1 support
Deployment Solution 6.9 supports Redhat Enterprise Server 5 update 1.
Windows CE 6.0 Thin Client support
Deployment Solution 6.9 provides an agent for the Thin Client Windows CE 6.0
operating system. This agent can manage the WinCE 6.0 based Thin Client using the
Deployment Console.
Macintosh OS X 10.5 support
Deployment Solution 6.9 supports OS X 10.5.
Remark :WinPE 2.1 is the only supported version
Deployment Solution 6.9 supports only WinPE 2.1. Since WinPE 2.1 is currently in
beta testing, it is available only to Microsoft beta customers and is not available for
general access.
If you have access to WAIK 2.1 we encourage you to use it. However, due to this
access limitation, this beta version of Deployment Solution supports WAIK 2.0 with
the following limitations:
• WAIK 2.0 does not provide support for Itanium systems.
• Non-RAM boot from CD is not supported. You can still create WinPE 2.0 boot
CDs, but you must select the Boot from RAM option in the Boot Disk Creator
when creating a WinPE 2.0 CD.
Deployment Solution 6.9 provides imaging and management support for Windows
Server 2008.
Agent support is provided using DAgent (first introduced on Windows Vista). DAgent
is fully functional on Windows Server 2008 and supports a full range of agent
functionality. DAgent runs on Win32, Win64 and IA64 Itanium platforms.
RDeploy, ImageX, and Ghost Imaging of Windows Server 2008
Deployment Solution 6.9 provides the ability to capture and deploy Windows Server
2008 images using RDeploy, ImageX, and Ghost using WinPE 2.1. ImageX and Ghost
support Win32 and Win64 platforms in WinPE 2.1.
RDeploy and Image X also provide Windows Server 2008 imaging support on
Itanium platforms, and RDeploy provides support for imaging from Linux automation.
Windows Server 2008 Scripted OS Install Job
Scripted server installations are supported for Windows Server 2008.
WinPE 2.1 Support (see below)
Deployment Solution 6.9 supports WinPE 2.1 for pre-boot and imaging tasks. Older
versions of WinPE are not supported.
Remote Agent install for Deployment Agent
Deployment Solution 6.9 introduces Remote agent install for Vista and Windows
Server 2008.
Support Views based on permission of Group
Deployment Solution 6.9 can restrict viewing of computers from unauthorized users,
based on their rights to manage a given computer. When a user without access
rights to a computer or group of computers logs in, those computers are not visible.
This is option is disabled by default.
VMWare Virtual Center 2.01 support
In the Deployment Console, you can add or import 1.x and 2.x virtual centers. These
virtual centers are displayed in a tree view as Rack and Blade enclosures do with a
visual relationship between the virtual center and the virtual machines that it hosts.
Administrators can visually distinguish a virtual center 1.x from a virtual center 2.x.
Scripted installations of VMWare ESX 3
Deployment Solution 6.9 provides support for scripted installations of VMWare ESX
Red Hat Enterprise Linux 5-update 1 support
Deployment Solution 6.9 supports Redhat Enterprise Server 5 update 1.
Windows CE 6.0 Thin Client support
Deployment Solution 6.9 provides an agent for the Thin Client Windows CE 6.0
operating system. This agent can manage the WinCE 6.0 based Thin Client using the
Deployment Console.
Macintosh OS X 10.5 support
Deployment Solution 6.9 supports OS X 10.5.
Remark :WinPE 2.1 is the only supported version
Deployment Solution 6.9 supports only WinPE 2.1. Since WinPE 2.1 is currently in
beta testing, it is available only to Microsoft beta customers and is not available for
general access.
If you have access to WAIK 2.1 we encourage you to use it. However, due to this
access limitation, this beta version of Deployment Solution supports WAIK 2.0 with
the following limitations:
• WAIK 2.0 does not provide support for Itanium systems.
• Non-RAM boot from CD is not supported. You can still create WinPE 2.0 boot
CDs, but you must select the Boot from RAM option in the Boot Disk Creator
when creating a WinPE 2.0 CD.
14 November 2007
Upgrade RDP (any version)
Before upgrading RDP make sure to unselect Secuirty in Tools-> Security
After the upgrade please select Enable Security again to reactivate security again
It fazils because the AXImport comment used in the scripts does ot have your security account.
After the upgrade please select Enable Security again to reactivate security again
It fazils because the AXImport comment used in the scripts does ot have your security account.
08 November 2007
Support for Windows 2008 and Vista SP1
Will Notification Server 7 support Windows 2008?
Will Notification Server 7 support Vista SP1?
Answer
The following information represents current expectations (as of Aug 2007) based upon Microsoft's estimated timelines and Altiris' estimated timelines for NS 7 release.
* NS7 will not initially support Windows 2008 as a host server. Current plan is to add support in a future version of NS7
* NS7 should support management of Windows 2008 (Altiris NS agent)
* NS7 should support management of Vista SP1 (Altiris NS agent)
Note: The last time this article was updated, Microsoft's eta for Windows 2008, and Vista SP1 was Q1 2008
Subscribe to:
Posts (Atom)