XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM

XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM

Scope:

Get the wizard to create VMs in Hyper-V

Details:

CDF shows:

SCVMM not returning a job ID

SCVMM has no record of the job

Wizard completes without error, but 1 machine fails

verfiying settings:

-Hyper V – on scvmm – posh execution policy – allow unrestricted – no chg

-create VMs manually from template – ok

-template settings – ok

-legacy nic 1st, synthetic nic 2nd

VMs a re-pooled w/ WC drive on template (on local storage)

VMM console installed on all DDCs

Related:

Manual generation of the App Layering agent self-signed certificate

A warning message similar to the below may be seen:

“Priority: High (Impact: Individual, Urgency: High)

Classification: Infrastructure Services, Server, Report an Issue

Description:

Event can not be resolved by the NOC and must be escalated. Please contact the NOC for additional information.

Event Error Message: Resolution state: New Source: Cert CN=UnideskAgent, O=Unidesk Corporation Alert: Certificate lifespan alert

Auto-created via rule: [SCOM] Catch-All

Alert: Certificate lifespan alert

Source: Cert CN=UnideskAgent, O=Unidesk Corporation

Path: [CustPVS_HostName]-INT.ORG;My

Last modified by: System

Last modified time: 11/25/2019 6:53:57 PM

Alert description: The certificate expires in 21 days on 12/18/2019 00:00:00 UTC.

Certificate Subject: CN=UnideskAgent, O=Unidesk Corporation

Certificate Issuer: CN=Unidesk Agent Temporary Authority, O=Unidesk Corporation

Serial number: 22C46BDE814CD3AD

Store Name: Personal

Store Key: My

Store Provider: SystemRegistry

Store Type: LocalMachine

Monitoring User: NT AUTHORITYSYSTEM

Chain Time Details:


“This message is intended for the use of the person or entity to which it is addressed and may contain information that is confidential or privileged, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you have received this message by error, please notify us immediately and destroy the related message.””

Related:

  • No Related Posts

App Layering: Backups with Microsoft DPM in Hyper-V cause the ELM boot disk to fill up

It appears that using Microsoft Data Protection Manager (DPM) to backup the ELM in Hyper-V can cause processes within the ELM to crash. When they do, they leave core files in folders in /var/crash. The system does not currently clean those up, so if your system generates new core files every night when DPM runs, you will soon fill up the disk.

First, delete the folders under /var/crash. They are not useful. Tools like FileZilla and WinSCP can do it remotely, or you can login as root and simply run:

cd /var/crash

rm -rf /var/crash/*

However, the long-term solution is to either find a backup solution other than DPM, or make sure the ELM is shut down while DPM runs (the ELM is not needed for any end-user VM operations, so it’s perfectly fine to shut it down or reboot it whenever you need to), or periodically look for and delete files in /var/crash. We are investigating why this happens and hope to update this article in the future.

Related:

Adding Microsoft System Center Virtual Machine Manager (SCVMM) as a VM Manager, similar to VMware vCenter

I was wondering if I can add Microsoft System Center Virtual Machine Manager (SCVMM) as a VM Manager, similar to how I’m able to add our vCenter Server to monitor all hosts managed by vCenter. I was hoping to avoid having to add each of our Hyper-V hosts manually, since we have over 50 hosts. Is there a way to do so?

Related:

Event ID 315 — Unicast Logging

Event ID 315 — Unicast Logging

Updated: August 14, 2009

Applies To: Windows Server 2008 R2

You can configure Logging plug-ins in Windows Media Services to keep a record, a log file, of client and server activity during a streaming session. Log information can also help:

  • Track server usage so that you can decide when you might need to add more resources to your system.
  • Assist you in planning your security implementation. For example, if your system is subjected to a denial-of-service attack, log files can help you determine which clients are being used in the attack.
  • Identify user-reported issues with your streaming system by providing event codes that correspond to common issues.
  • Provide historical data for use in trend analysis and business cases.

For more information, see Logging Model for Windows Media Services.

Event Details

Product: Windows Media Services
ID: 315
Source: WMServer
Version: 9.6
Symbolic Name: WMS_EVMSG_LOGGING_DEFAULT_FILE_USED
Message: The WMS Client Logging plug-in is logging data using the default file name template for the unicast log file ‘%1’. A directory was specified as the log file name.

Resolve
Update the unicast logging path template

To configure the path template for unicast logging:

  1. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server or the on-demand publishing point for which you want to log data.
  3. In the details pane, click the Properties tab.
  4. In Category, click Logging.
  5. In Plug-in, right-click WMS Client Logging, and then click Properties.
  6. In the WMS Client Logging Properties dialog box, in Directory, enter the path and name for the log file. For more information, see WMS Client Logging.
  7. Click OK to save the changes.

Verify

To verify that the client logs are being created correctly, test a stream by using Windows Media Player:

  1. If you want to test the stream by using Windows Media Player on the computer that is running Windows Media Services, you must install Desktop Experience. For more information, see Installing Desktop Experience.
  2. In Windows Media Services, in the console tree, click the publishing point that hosts a stream that you want to test.
  3. In the details pane, click the Announce tab, and then, in Connect to a unicast stream, note the value of the URL that a client can use to access the content.
  4. Start Windows Media Player on a computer that can access the stream, and enter the URL that you noted in the previous step.
  5. Using the Player controls, test the control functionality of the content stream. Broadcast streams can use the Start and Stop commands. On-demand streams can use the Start, Stop, and Pause commands, and the Seek bar.
  6. Test all the available streaming protocols. A unicast stream will try to connect by using the MMS protocol, but will switch to the RTSP protocol if network conditions or the Player version requires it. The HTTP protocol is not active unless the WMS HTTP Server Control Protocol plug-in is enabled. For more information, see About data transfer protocols.
  7. Allow the stream to play for a representative period of time and check that the stream quality is sufficient for the type of content and the capabilities of the equipment.
  8. View the fields in the log file to confirm that they are filled in correctly. For more information, see Log File Entries Reference.

Note: You can use a Globally Unique Identifier (GUID) value created by Windows Media Player to identify the Player connection to the Windows Media server and view the log entries created by the Player that you use in your test environment. The c-playerid field in the log is used to record the Player ID value. To help protect user privacy, the option to send unique Player identification information to content providers is turned off in Windows Media Player. For Player log entries, if the Player is configured to not send this information, the recorded value in c-playerid is: {3300AD50-2C39-46c0-AE0A-xxxxxxxxxxxx}, where x is the session ID of the client. To identify the log entries generated by the Player in your test environment, you can enable the option to send a unique Player ID on the Privacy tab in Windows Media Player. For more information, see the Windows Media Player Privacy Statement.

Related Management Information

Unicast Logging

Streaming Media Services

Related:

MSMQT static data in the database is written by an incompatible version.

Details
Product: BizTalk Server
Event ID: 7464
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: MSMQT static data in the database is written by an incompatible version.
   
Explanation
BizTalk Server 2004 database was created by an older version of BizTalk Server and must be configured for BizTalk Server 2004.
   
User Action
Reconfigure your BizTalk Server 2004 databases.

Related:

MSMQT failed to get current networking parameters

Details
Product: BizTalk Server
Event ID: 7461
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: MSMQT failed to get current networking parameters
   
Explanation
BizTalk Server 2004 was unable to obtain the current networking parameters (for example, the host name, IP, and so forth) from the operating system.
   
User Action
Verify health of the system.

Related:

The MSMQT subservice failed to start because Windows MSMQ service is running on the computer.

Details
Product: BizTalk Server
Event ID: 7425
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: The MSMQT subservice failed to start because Windows MSMQ service is running on the computer.
   
Explanation
MSMQ (Windows service) cannot run in parallel with BizTalk Server on the same machine unless both MSMQ and BizTalk Server are configured specifically to work together. The configuration requires MSMQ and BizTalk to run on a separate IP address.
   
User Action
If your computer does not require MSMQ service, use Computer Management to disable the Message Queueing service for Windows. If you require MSMQ and BizTalk Server to work side by side, refer to the BizTalk Server 2004 documentation for instructions on co

Related:

Multi-dimensional arrays are not supported in property values

Details
Product: BizTalk Server
Event ID: 6964
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: Multi-dimensional arrays are not supported in property values
   
Explanation

Multi-dimensional arrays are not supported in property values.

   
User Action
Check the schema for supported types.

Related: