Article ID: 299772 - Last Review: October 25, 2006 - Revision: 2.3 Site-Wide Travel mode prevents Windows NT remote client installationThis article was previously published under Q299772 SYMPTOMS
When you configure a Systems Management Server (SMS) site with site-wide Traveling mode set to "always on", Windows NT Remote Client Installation does not work and the following message is logged in the Ccm.log file if logging is enabled:
---> Travel mode is turned ON & the client is NOT currently assigned to this site. Discarding CCR
CAUSE
The following scenario causes Client Configuration Requests (CCRs) to be abandoned, therefore preventing Windows NT Remote Client Installation:
RESOLUTIONTo resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
288239
(http://support.microsoft.com/kb/288239/EN-US/
)
SMS: How to Obtain the Latest Systems Management Server 2.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Systems Management Server 2.0 Service Pack 4. MORE INFORMATION
The following article describes SMS Traveling mode and the SMS Support tools, Chktravl.bat and Clitravl.exe:
199114
(http://support.microsoft.com/kb/199114/EN-US/
)
How to Configure Traveling Mode on Client Computers
Traveling Mode is an SMS client registry setting that dictates the SMS client behavior for mobile clients when they enter the boundary of a site to which they are not currently assigned. Traveling mode is discussed in the Traveling Mode section in chapter 9 of the Microsoft Systems Management Server Administrator's guide. There are three ways to modify Traveling mode, each with increasing levels of granularity:
APPLIES TO
| Article Translations
|
Back to the top
