You will receive a errors in the system log indicating the server was not shutdown gracefully and blue screen has occurred with memory dump being created.
Workaround
Untick Microsoft Network Monitor 3 Driver from Heartbeat network interfaces. This allows the server to shutdown correctly and not bluescreen.
1. Move all Service groups to another node, so no resource are on the server we are making changes to.
2. Stop HAD by opening command prompt and type hastop -local -force. Then stop llt, gab and vcscomm.
============================================
C:\Windows\system32>hastop -local -force
C:\Windows\system32>net stop llt
The following services are dependent on the LLT service.
Stopping the LLT service will also stop these services.
Veritas VCSComm Startup
GAB
Do you want to continue this operation? (Y/N) [N]: y
The Veritas VCSComm Startup service was stopped successfully.
The GAB service was stopped successfully.
The LLT service was stopped successfully.
==============================================
3. Go to network properties and change adapter settings. Select heartbeat network interface and view properties.
4. Untick Network Monitor 3 Driver and select OK. Perform steps 2 and 3 for any other heartbeat network interfaces.
5. Start HAD on the server again. This will also start LLT, GAB and VCSComm services.
C:\Windows\system32>hastart
VCS INFO V-16-1-11020 Starting HAD on local node
6. Restart server and confirm server is able to shutdown gracefully.
Note: If unticking Microsoft Network Monitor 3 Driver while LLT is started the Local Area Connection Properties dialog box will hang until you stop LLT.
Applies To
Veritas Version: Storage Foundation HA for Windows 5.1 SP2
OS Version: Windows server 2008 R2 SP2
Application: Microsoft Network Monitor 3.4