Contents
-
Introducing Nomad 7.0.200
-
Implementing Nomad
-
Working with Nomad
-
Troubleshooting
-
Training
-
Reference
-
Supported Platforms
-
Server sizing
-
Communication ports
-
Nomad installer properties
-
Nomad registry values
-
Alphabetic NomadBranch registry values
-
AssumedLinkSpeed
-
AuthenticatedUsers
-
BlockSize
-
CacheCleanCycleHrs
-
CachePath
-
CentralMCastExtraDelayMins
-
CertIssuer
-
CertSubject
-
CompatibilityFlags
-
ContentProviderOnWifi
-
ContentRegistration
-
ContentRegSyncBatchSz
-
ContentRegSyncCycleHrs
-
ContentRegSyncReqDelay
-
Debug
-
DebugDynamicBlock
-
DownloadTimeout
-
DpCacheCleanupEnabled
-
DPNotAvailableCodes
-
EncryptionType
-
EnforceQuotas
-
ExtraReplyDelayMs
-
GenerateWEREvents
-
HAACKTimeoutMins
-
InstallationDirectory
-
KnownMobileDevices
-
LocalCachePath
-
LocalSsdStagger
-
LogFileName
-
MaxAllocRequest
-
MaxAllowedLinkSpeed
-
MaxBusyBackOffSecs
-
MaxCacheDays
-
MaxCacheSizeMB
-
MaxConcurrency
-
MaxDevicesFromAE
-
MaxElectionResponseLogging
-
MaximumMegaByte
-
MaxLogFileSize
-
MaxPackageSizeFastLAN
-
MaxPackageSizeRAS
-
MaxPackageSizeSlowLAN
-
MaxPacketsPerSecond
-
MaxPreCacheDays
-
MaxStatusFrequency
-
MaxStuckCount
-
MaxSUCacheDays
-
MaxWorkRates
-
MultiCastMADCAPScope
-
MulticastSupport
-
NoHardlink
-
NomadInhibitedADSites
-
NomadInhibitedSubnets
-
NomadNeverUseSubnets
-
NoSsdReqOnInhibitedSubnets
-
P2P_Port
-
P2PClientCertWaitPeriodMins
-
P2PDisqualifyMaxNumPeers
-
P2PDisqualifyMaxWindowMins
-
P2PElectionWeight
-
P2PEnabled
-
P2PHttpPort
-
P2PHttpsPort
-
P2PSslSettings
-
PercentAvailableDisk
-
PercentDelayedContentReg
-
PermittedLSZShares
-
PlatformURL
-
PostCompleteTimeoutHours
-
PrecachePollBatchSize
-
PrecachePollMinutes
-
PreCompleteTimeoutHours
-
RecycleDPDelay
-
RunUncachedPermittedFastLAN
-
SigsFolder
-
SiteSsdStagger
-
SpecialNetShare
-
SSDEnabled
-
SSPBAEnabled
-
StatusMsgEvents
-
SuccessCodes
-
WakeUpBatchSize
-
WakeUpEnabled
-
WakeUpMinPackageSizeMB
-
WLanBlipSecs
-
WLanProfileList
-
AssumedLinkSpeed
-
Nomad client registry values and installer properties
-
Alphabetic NomadBranch registry values
-
Nomad command-line switches
-
Nomad return codes
-
Status messages for download events
-
Nomad local multicast
-
Basic Nomad behavior in a simple environment
-
Index
-
Release notes
-
Log files
-
Supported Platforms
Registry value | Default value | Notes | Installer property | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
StatusMsgEvents | 0x0 | Status message events should be used with caution as they could impact your Configuration Manager environment when scaled up to tens of thousands of machines. They are provided mainly for advanced troubleshooting purposes, although some events are also used to support the Nomad dashboard tiles.
SNO_EVT_FINALSTATS notesFor success reporting, this message provides feedback on the status of the download. For example, it can show how much data was received using multicast as opposed to peer-to-peer copying. Turning this message on creates an extra status message per machine for each deployment. The format of the status message is: Evt_FinalStats MD100067 1 170 59195038 170 59195038 0 59195038 0 0 Configuration Manager status messages are made up of insertion strings. The strings for the final stats event are:
If the package is already cached and is re-deployed with an unchanged package version, the final stats message will not be re-sent. The Nomad Dashboard Latest Operations tilesNomad clients must be configured to return the following status messages into the Configuration Manager site database in order to populate the Nomad dashboard's Latest Operations tiles. Because the Nomad client does not return any status messages by default, you must configure the Nomad client registry StatusMsgEvents value, either during installation of 1E Client or using The Nomad Baseline Wizard.
These combine to the following value: | MODULE.NOMAD.STATUSMSGEVENTS |