From any PVS server in the farm, browse to the C:\Program Files\Citrix\Provisioning Services Console directory via command prompt and run the following
mcli run markdown /p servername="name"
replace the "name" with the server that is no longer used, once you do this browse through the console, find the server, right click, delete.
Showing posts with label PVS Server. Show all posts
Showing posts with label PVS Server. Show all posts
Wednesday, 16 March 2011
Tuesday, 21 September 2010
Enabling better PVS Logs
ere how to turn on better logging:
Console log file: “c:\documents and settings\all users\application data\citrix\provisioning server\eeapi.log”
Config file: “c:\program files\citrix\provisioning server console\enterpriseaccess_log.config”
Stream process log file: “c:\documents and settings\all users\application data\citrix\provisioning server\stream.log”
Config file: “c:\program files\citrix\provisioning server\stream_log.config”
Soap server log file: “c:\documents and settings\all users\application data\citrix\provisioning server\soapserver.log”
Config file: “c:\program files\citrix\provisioning server\soapserver_log.config”
MCLI log file: “c:\documents and settings\all users\application data\citrix\provisioning server\mcli.log”
Config file: “c:\program files\citrix\provisioning server\mcli_log.config”
In each case, the .config file controls the level output according to the “level value” entry towards the bottom of the file:
The three levels are ERROR, DEBUG and TRACE with ERROR being the default value installed with the product. DEBUG will be the most useful for diagnosing customer issues. The corresponding service does not require restarting after the log level has been changed.
Get some logs and we can start to troubleshoot.
Console log file: “c:\documents and settings\all users\application data\citrix\provisioning server\eeapi.log”
Config file: “c:\program files\citrix\provisioning server console\enterpriseaccess_log.config”
Stream process log file: “c:\documents and settings\all users\application data\citrix\provisioning server\stream.log”
Config file: “c:\program files\citrix\provisioning server\stream_log.config”
Soap server log file: “c:\documents and settings\all users\application data\citrix\provisioning server\soapserver.log”
Config file: “c:\program files\citrix\provisioning server\soapserver_log.config”
MCLI log file: “c:\documents and settings\all users\application data\citrix\provisioning server\mcli.log”
Config file: “c:\program files\citrix\provisioning server\mcli_log.config”
In each case, the .config file controls the level output according to the “level value” entry towards the bottom of the file:
The three levels are ERROR, DEBUG and TRACE with ERROR being the default value installed with the product. DEBUG will be the most useful for diagnosing customer issues. The corresponding service does not require restarting after the log level has been changed.
Get some logs and we can start to troubleshoot.
Subscribe to:
Posts (Atom)