Evening all!
So recently upgraded Vcenter to 5.1 and also View to 5.2, with upgrades of both our viewSecurity and viewComposer servers.
All went well and builds are correctly listed.
In a test pool creation of our first linked-clone Master image, I followed the Windows 7 Optimisation guide from VMware here:
http://www.vmware.com/files/pdf/VMware-View-OptimizationGuideWindows7-EN.pdf.
After running the 'nopersonacommands.bat' on my master image, I can no longer connect via the HTML access portal, I.e through a browser (blast in view 5.2). The blast log is below:
2013-03-18 13:46:25,767 [INFO ] 0x00000178 main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=940, mode=service) 2013-03-18 13:46:25,814 [INFO ] 0x00000178 MainApp::MainApp: Now running on session ID 0. 2013-03-18 13:46:25,814 [DEBUG] 0x00000178 config::NewInstance: New instance for PID 940, isUser=false 2013-03-18 13:46:25,829 [INFO ] 0x00000178 main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 13:46:25,829 [INFO ] 0x00000178 winService::RunAsService: Starting the service ... 2013-03-18 13:46:25,829 [INFO ] 0x00000488 MainApp::OnStart: Starting VMware Blast... 2013-03-18 13:46:25,829 [INFO ] 0x00000488 MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 13:46:25,829 [DEBUG] 0x00000488 pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 13:46:25,829 [DEBUG] 0x00000488 pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 13:46:25,829 [INFO ] 0x00000488 workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 13:46:25,845 [INFO ] 0x0000073c workerProcessMgr::DumpWTSState: Session 1 (Console) in state 0, logged in as 'administrator' 2013-03-18 13:46:25,845 [INFO ] 0x0000073c workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 13:46:25,860 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 13:46:25,860 [INFO ] 0x0000073c workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 13:46:25,860 [INFO ] 0x0000073c workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 13:46:25,860 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 13:46:35,166 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 40010004. 2013-03-18 13:46:35,166 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: Worker process exited via logoff. Waiting for logoff to complete. 2013-03-18 13:46:42,593 [INFO ] 0x00000178 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGOFF 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 13:46:45,270 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 13:47:03,926 [INFO ] 0x00000178 MainApp::OnStop: Stopping VMware Blast... 2013-03-18 13:47:03,926 [INFO ] 0x00000178 MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 13:47:03,926 [DEBUG] 0x0000073c pipelib::PipeLog: PipeClient: Wrote 17 bytes to client pipe. 2013-03-18 13:47:03,926 [DEBUG] 0x000004e4 pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 13:47:04,004 [DEBUG] 0x0000073c pipelib::PipeLog: PipeClient: Read 3 bytes from client pipe. 2013-03-18 13:47:04,004 [ERROR] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: Got unexpected response from worker: 'OK' 2013-03-18 13:47:04,440 [INFO ] 0x0000073c workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 00000000. 2013-03-18 13:47:04,440 [INFO ] 0x00000178 workerProcessMgr::Shutdown: WorkerProcessMgr monitoring thread is shutdown. 2013-03-18 13:47:04,456 [INFO ] 0x00000178 main::__stdcall wWinMain: VMware Blast shutdown. 2013-03-18 13:48:14,408 [INFO ] 0x000006d0 main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=1496, mode=service) 2013-03-18 13:48:14,564 [INFO ] 0x000006d0 MainApp::MainApp: Now running on session ID 0. 2013-03-18 13:48:14,564 [DEBUG] 0x000006d0 config::NewInstance: New instance for PID 1496, isUser=false 2013-03-18 13:48:14,564 [INFO ] 0x000006d0 main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 13:48:14,564 [INFO ] 0x000006d0 winService::RunAsService: Starting the service ... 2013-03-18 13:48:14,564 [INFO ] 0x000006f8 MainApp::OnStart: Starting VMware Blast... 2013-03-18 13:48:14,564 [INFO ] 0x000006f8 MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 13:48:14,610 [DEBUG] 0x000006f8 pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 13:48:14,610 [DEBUG] 0x000006f8 pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 13:48:14,610 [INFO ] 0x000006f8 workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 13:48:14,673 [INFO ] 0x00000598 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 13:48:14,673 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 13:48:14,673 [INFO ] 0x00000598 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 13:48:14,688 [INFO ] 0x00000598 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 13:48:14,688 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 13:48:17,624 [INFO ] 0x000006d0 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGON 2013-03-18 13:54:34,984 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 40010004. 2013-03-18 13:54:34,984 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: Worker process exited via logoff. Waiting for logoff to complete. 2013-03-18 13:54:36,912 [INFO ] 0x000006d0 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGOFF 2013-03-18 13:54:37,965 [INFO ] 0x00000598 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 8, logged in as '' 2013-03-18 13:54:37,980 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 13:54:37,980 [INFO ] 0x00000598 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 13:54:37,980 [INFO ] 0x00000598 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 13:54:37,980 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 13:54:38,074 [INFO ] 0x000006d0 MainApp::OnStop: Stopping VMware Blast... 2013-03-18 13:54:38,074 [INFO ] 0x000006d0 MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 13:54:38,074 [DEBUG] 0x000006f0 pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 13:54:39,275 [DEBUG] 0x00000598 pipelib::PipeLog: PipeClient: Wrote 17 bytes to client pipe. 2013-03-18 13:54:46,201 [DEBUG] 0x00000598 pipelib::PipeLog: PipeClient: Read from client pipe failed (0x0000006d). 2013-03-18 13:54:46,201 [ERROR] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: Could not send stop message to worker, err=0x0000006d 2013-03-18 13:54:46,201 [INFO ] 0x00000598 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 000056b8. 2013-03-18 13:54:46,201 [INFO ] 0x000006d0 workerProcessMgr::Shutdown: WorkerProcessMgr monitoring thread is shutdown. 2013-03-18 13:54:46,201 [INFO ] 0x000006d0 main::__stdcall wWinMain: VMware Blast shutdown. 2013-03-18 16:05:06,764 [INFO ] 0x000007ac main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=1976, mode=service) 2013-03-18 16:05:06,873 [INFO ] 0x000007ac MainApp::MainApp: Now running on session ID 0. 2013-03-18 16:05:06,873 [DEBUG] 0x000007ac config::NewInstance: New instance for PID 1976, isUser=false 2013-03-18 16:05:06,873 [INFO ] 0x000007ac main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 16:05:06,873 [INFO ] 0x000007ac winService::RunAsService: Starting the service ... 2013-03-18 16:05:06,873 [INFO ] 0x000007ec MainApp::OnStart: Starting VMware Blast... 2013-03-18 16:05:06,889 [INFO ] 0x000007ec MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 16:05:06,967 [DEBUG] 0x000007ec pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 16:05:06,982 [DEBUG] 0x000007ec pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 16:05:06,982 [INFO ] 0x000007ec workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 16:05:06,998 [INFO ] 0x000007d0 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 16:05:06,998 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 16:05:06,998 [INFO ] 0x000007d0 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 16:05:06,998 [INFO ] 0x000007d0 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 16:05:06,998 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 16:06:07,599 [INFO ] 0x000007ac winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGON 2013-03-18 16:19:26,905 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 40010004. 2013-03-18 16:19:26,905 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: Worker process exited via logoff. Waiting for logoff to complete. 2013-03-18 16:19:28,862 [INFO ] 0x000007ac winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGOFF 2013-03-18 16:19:30,811 [INFO ] 0x000007d0 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 8, logged in as '' 2013-03-18 16:19:31,154 [INFO ] 0x000007ac MainApp::OnStop: Stopping VMware Blast... 2013-03-18 16:19:31,154 [INFO ] 0x000007ac MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 16:19:31,154 [DEBUG] 0x000007e0 pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 16:19:31,154 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 16:19:31,154 [INFO ] 0x000007d0 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 16:19:31,154 [INFO ] 0x000007d0 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 16:19:31,154 [INFO ] 0x000007d0 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 17:03:19,465 [INFO ] 0x00000f90 main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=3980, mode=service) 2013-03-18 17:03:19,573 [INFO ] 0x00000f90 MainApp::MainApp: Now running on session ID 0. 2013-03-18 17:03:19,573 [DEBUG] 0x00000f90 config::NewInstance: New instance for PID 3980, isUser=false 2013-03-18 17:03:19,573 [INFO ] 0x00000f90 main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 17:03:19,573 [INFO ] 0x00000f90 winService::RunAsService: Starting the service ... 2013-03-18 17:03:19,573 [INFO ] 0x00000fc8 MainApp::OnStart: Starting VMware Blast... 2013-03-18 17:03:19,573 [INFO ] 0x00000fc8 MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 17:03:19,573 [DEBUG] 0x00000fc8 pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 17:03:19,573 [DEBUG] 0x00000fc8 pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 17:03:19,573 [INFO ] 0x00000fc8 workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 17:03:19,589 [INFO ] 0x00000fd0 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 0, logged in as 'Administrator' 2013-03-18 17:03:19,589 [INFO ] 0x00000fd0 workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 17:03:19,589 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 17:03:19,589 [INFO ] 0x00000fd0 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 17:03:19,604 [INFO ] 0x00000fd0 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 17:03:19,604 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 17:03:33,957 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 40010004. 2013-03-18 17:03:33,957 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: Worker process exited via logoff. Waiting for logoff to complete. 2013-03-18 17:03:36,093 [INFO ] 0x00000f90 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGOFF 2013-03-18 17:03:37,135 [INFO ] 0x00000fd0 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 8, logged in as '' 2013-03-18 17:03:37,135 [ERROR] 0x00000fd0 workerProcessMgr::DumpWTSState: WTSQuerySessionInformation failed, err = 1717 2013-03-18 17:03:37,135 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 17:03:37,151 [INFO ] 0x00000fd0 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 17:03:37,151 [INFO ] 0x00000fd0 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 17:03:37,151 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 17:03:38,742 [INFO ] 0x00000f90 MainApp::OnStop: Stopping VMware Blast... 2013-03-18 17:03:38,742 [INFO ] 0x00000f90 MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 17:03:38,742 [DEBUG] 0x00000fd0 pipelib::PipeLog: PipeClient: Wrote 17 bytes to client pipe. 2013-03-18 17:03:38,742 [DEBUG] 0x00000fcc pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 17:03:42,158 [DEBUG] 0x00000fd0 pipelib::PipeLog: PipeClient: Read from client pipe failed (0x0000006d). 2013-03-18 17:03:42,158 [ERROR] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: Could not send stop message to worker, err=0x0000006d 2013-03-18 17:03:42,158 [INFO ] 0x00000fd0 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 000056b8. 2013-03-18 17:03:42,158 [INFO ] 0x00000f90 workerProcessMgr::Shutdown: WorkerProcessMgr monitoring thread is shutdown. 2013-03-18 17:03:42,158 [INFO ] 0x00000f90 main::__stdcall wWinMain: VMware Blast shutdown. 2013-03-18 18:35:22,801 [INFO ] 0x00000680 main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=1660, mode=service) 2013-03-18 18:35:22,863 [INFO ] 0x00000680 MainApp::MainApp: Now running on session ID 0. 2013-03-18 18:35:22,863 [DEBUG] 0x00000680 config::NewInstance: New instance for PID 1660, isUser=false 2013-03-18 18:35:22,863 [INFO ] 0x00000680 main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 18:35:22,863 [INFO ] 0x00000680 winService::RunAsService: Starting the service ... 2013-03-18 18:35:22,879 [INFO ] 0x0000077c MainApp::OnStart: Starting VMware Blast... 2013-03-18 18:35:22,879 [INFO ] 0x0000077c MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 18:35:22,957 [DEBUG] 0x0000077c pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 18:35:22,957 [DEBUG] 0x0000077c pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 18:35:22,957 [INFO ] 0x0000077c workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 18:35:23,097 [INFO ] 0x000004e4 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 18:35:23,113 [INFO ] 0x000004e4 workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 18:35:23,113 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 18:35:23,113 [INFO ] 0x000004e4 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 18:35:23,113 [INFO ] 0x000004e4 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 18:35:23,113 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 18:35:24,962 [INFO ] 0x00000680 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGON 2013-03-18 18:54:55,077 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 40010004. 2013-03-18 18:54:55,077 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: Worker process exited via logoff. Waiting for logoff to complete. 2013-03-18 18:54:56,975 [INFO ] 0x00000680 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOGOFF 2013-03-18 18:54:57,984 [INFO ] 0x00000680 MainApp::OnStop: Stopping VMware Blast... 2013-03-18 18:54:57,984 [INFO ] 0x00000680 MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 18:54:57,984 [DEBUG] 0x000004ec pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 18:54:57,984 [INFO ] 0x000004e4 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 8, logged in as '' 2013-03-18 18:54:57,984 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 18:54:57,984 [INFO ] 0x000004e4 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 18:54:57,984 [INFO ] 0x000004e4 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 18:54:57,984 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 18:54:59,154 [DEBUG] 0x000004e4 pipelib::PipeLog: PipeClient: Wrote 17 bytes to client pipe. 2013-03-18 18:55:01,790 [DEBUG] 0x000004e4 pipelib::PipeLog: PipeClient: Read from client pipe failed (0x0000006d). 2013-03-18 18:55:01,790 [ERROR] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: Could not send stop message to worker, err=0x0000006d 2013-03-18 18:55:01,790 [INFO ] 0x000004e4 workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 000056b8. 2013-03-18 18:55:01,790 [INFO ] 0x00000680 workerProcessMgr::Shutdown: WorkerProcessMgr monitoring thread is shutdown. 2013-03-18 18:55:01,806 [INFO ] 0x00000680 main::__stdcall wWinMain: VMware Blast shutdown. 2013-03-18 19:05:52,549 [INFO ] 0x0000074c main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=1864, mode=service) 2013-03-18 19:05:52,565 [INFO ] 0x0000074c MainApp::MainApp: Now running on session ID 0. 2013-03-18 19:05:52,565 [DEBUG] 0x0000074c config::NewInstance: New instance for PID 1864, isUser=false 2013-03-18 19:05:52,565 [INFO ] 0x0000074c main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 19:05:52,565 [INFO ] 0x0000074c winService::RunAsService: Starting the service ... 2013-03-18 19:05:52,565 [INFO ] 0x000000fc MainApp::OnStart: Starting VMware Blast... 2013-03-18 19:05:52,581 [INFO ] 0x000000fc MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 19:05:52,581 [DEBUG] 0x000000fc pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 19:05:52,581 [DEBUG] 0x000000fc pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 19:05:52,581 [INFO ] 0x000000fc workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 19:05:52,643 [INFO ] 0x0000052c workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 19:06:27,553 [INFO ] 0x0000074c MainApp::OnStop: Stopping VMware Blast... 2013-03-18 19:06:27,554 [INFO ] 0x0000074c MainApp::OnStop: Service is now shutting down the worker process. 2013-03-18 19:06:27,554 [DEBUG] 0x0000052c pipelib::PipeLog: PipeClient: Wrote 17 bytes to client pipe. 2013-03-18 19:06:27,555 [DEBUG] 0x00000530 pipelib::PipeLog: PipeServer: Exiting thread due to stop event! 2013-03-18 19:06:27,753 [DEBUG] 0x0000052c pipelib::PipeLog: PipeClient: Read 3 bytes from client pipe. 2013-03-18 19:06:27,753 [ERROR] 0x0000052c workerProcessMgr::CreateWorkerAndMonitor: Got unexpected response from worker: 'OK' 2013-03-18 19:06:27,935 [INFO ] 0x0000052c workerProcessMgr::CreateWorkerAndMonitor: A worker process exited with error code: 00000000. 2013-03-18 19:06:27,936 [INFO ] 0x0000074c workerProcessMgr::Shutdown: WorkerProcessMgr monitoring thread is shutdown. 2013-03-18 19:06:27,937 [INFO ] 0x0000074c main::__stdcall wWinMain: VMware Blast shutdown. 2013-03-18 20:06:57,497 [INFO ] 0x00000698 main::__stdcall wWinMain: VMware Blast version 1.0.0-1045852, build1045852 starting up (pid=1680, mode=service) 2013-03-18 20:06:57,515 [INFO ] 0x00000698 MainApp::MainApp: Now running on session ID 0. 2013-03-18 20:06:57,515 [DEBUG] 0x00000698 config::NewInstance: New instance for PID 1680, isUser=false 2013-03-18 20:06:57,515 [INFO ] 0x00000698 main::__stdcall wWinMain: Running VMware Blast as Windows service. 2013-03-18 20:06:57,515 [INFO ] 0x00000698 winService::RunAsService: Starting the service ... 2013-03-18 20:06:57,938 [INFO ] 0x000005c8 MainApp::OnStart: Starting VMware Blast... 2013-03-18 20:06:57,938 [INFO ] 0x000005c8 MainApp::OnStart: Service is now spawning a worker process. 2013-03-18 20:06:57,938 [DEBUG] 0x000005c8 pipelib::PipeLog: PipeSecurityAttrLocalSystem: Created SECURITY_ATTRIBUTES for "Local System" 2013-03-18 20:06:57,938 [DEBUG] 0x000005c8 pipelib::PipeLog: PipeServer: Server pipe \\.\pipe\ab_int_wtos_pipe created, waiting for clients 2013-03-18 20:06:57,938 [INFO ] 0x000005c8 workerProcessMgr::Start: WorkerProcessMgr monitoring thread started. 2013-03-18 20:06:58,539 [INFO ] 0x00000524 workerProcessMgr::DumpWTSState: Session 1 (Console) in state 1, logged in as '' 2013-03-18 20:06:58,540 [INFO ] 0x00000524 workerProcessMgr::DumpWTSState: Session 65536 (RDP-Tcp) in state 6, logged in as '' 2013-03-18 20:06:58,637 [INFO ] 0x00000524 workerProcessMgr::CreateWorkerAndMonitor: User/console session ID is 1. 2013-03-18 20:06:58,637 [INFO ] 0x00000524 workerProcessMgr::CreateProcessInInteractiveSession: Console session id: 1. 2013-03-18 20:06:58,639 [INFO ] 0x00000524 workerProcessMgr::CreateProcessInInteractiveSession: CreateProcessWithToken "C:\Program Files\VMware\VMware Blast\Blast.exe" -worker succeeded 2013-03-18 20:06:58,639 [INFO ] 0x00000524 workerProcessMgr::CreateWorkerAndMonitor: A new worker process is created in the user/console session. 2013-03-18 20:07:46,051 [INFO ] 0x00000698 winService::ServiceCtrlHandlerI nst: WTS_SESSION_LOGON 2013-03-18 20:10:18,550 [INFO ] 0x00000698 winService::ServiceCtrlHandlerInst: WTS_SESSION_LOCK 2013-03-18 20:10:19,646 [INFO ] 0x00000698 winService::ServiceCtrlHandlerInst: WTS_SESSION_UNLOCK
I noiced on first check of my master image that windows
firewall service was off and turned the service back on, making it an auto-start. On recomposing the image in View 5.2, the pool was rebuilt, but
nothing!
The error statements don't really make sense above, any ideas??
My thoughts are that the Windows 7 optimisation guide commands have stopped a potential dependency?
Thanks in advance 
Athemiya