KNOWN ISSUE: The query for the token ''NSSERVERNAME'' is incorrect and does not work in a hierarchy
|Article:TECH127612|||||Created: 2010-05-21|||||Updated: 2010-05-21|||||Article URL http://www.symantec.com/docs/TECH127612|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
In a hierarchical environment, the 'NSSERVERNAME' token does not return the correct site server for the client to access.
Notification Server 7.0 SP4
Deployment Solution 7.1
The SQL query behind that makes the 'NSSERVERNAME' token is incorrect.
To resolve this issue please do the following:
1) Open the Symantec Management Console and click on 'Settings' > 'All Settings'.
2) In the left hand pane expand the folders to the 'Notification Server' > 'Task Settings' folder
3) From the right hand panel double click 'NS Server name'
4) Copy the current SQL statement displayed to a notepad file (for backup purposes).
5) Replace the current SQL query with the SQL query below:
select [Server] from [vComputer] where [Guid] = '%COMPUTERID%'
6) In the 'Token name' field rename the token to 'NSServername'
7) Click on 'Save changes'8) Double click on 'NS Server name'. The 'Token name' will now be 'NS Server name'
|Description||Logged in Etrack (Symantec) database|
Article URL http://www.symantec.com/docs/TECH127612