How to to add more than 200 VM’s in machine catalog when using Azure as hosting unit


Add a custom property to the catalog properties.

  • Retrieve the existing custom properties of the catalog:

> Get-ProvScheme -ProvisioningSchemeName “catalog name”

  • Copy the Custom Properties XML to clipboard
  • Define a set of custom properties including the new property:

> $customProperties = ‘ copy updated custom properties ‘

  • Paste the XML between the ” characters above, and insert the text ‘<Property xsi:type=”IntProperty” Name=”StorageAccountsPerResourceGroup” Value=”7″/> into the property set, e.g.:

$customProperties = “<CustomProperties xmlns=”http://schemas.citrix.com/2014/xd/machinecreation” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“><Property xsi:type=”StringProperty” Name=”UseManagedDisks” Value=”false” /><Property xsi:type=”StringProperty” Name=”StorageAccountType” Value=”Premium_LRS” /><Property xsi:type=”StringProperty” Name=”ResourceGroups” Value=”pmcs-6102-resource-group-2a,pmcs-6102-resource-group-2b” /><Property xsi:type=”IntProperty” Name=”StorageAccountsPerResourceGroup” Value=”7″/></CustomProperties>”

(don’t copy the above verbatim, it’s an example)

  • Assign the new set of custom properties to the provisioning scheme

> Set-ProvScheme -ProvisioningSchemeName “ProvisioningSchemeNameToEdit” -CustomProperties $customProperties

Related:

7021323: Web Services Target Namespace in Verastream Host Integrator

Default Values

The following table lists the default target namespace values by VHI product version:

VHI Version
Type
WSDL Default Target Namespace
7.5 SP1 or higher
(Any)
urn:xmlns:attachmate:vhi-ws:<model name>
7.0 – 7.5
Pooled
urn:xmlns:attachmate:vhi-ws:session:<pool name>
7.0 – 7.5
Non-pooled (model)
urn:xmlns:attachmate:vhi-ws:model:<model name>
6.6.189 – 6.6.222
.NET and Java
urn:xmlns:attachmate:vhi-wb-ws:<project name>
5.5 – 6.6.188
.NET
http://tempuri.org/
5.0 – 6.6.188
Java
http://<host name>:<port>/axis/services/<project name>

Customizing the Target Namespace

There are several methods available for modifying the namespace, depending on your product version.

Administrative Console

Beginning in version 7.5 SP1, you can set a custom target namespace prefix in Administrative Console (in Session Server Properties > Web Services). The model name gets appended to this prefix. Note: Beginning in version 7.7, this option is no longer recommended.

Beginning in version 7.7, you can view and set model- and pool-specific custom namespaces in Administrative Console (in Model Properties and Pool Properties respectively). Note: Values set in Administrative Console may be overwritten by subsequent model deployment.

Deployment Descriptor

Beginning in version 7.7, you can set a model- or pool-specific custom namespace in the model deployment descriptor (deploy_desc.xml file). In the <model-configuration> or <pool-configuration> node (just before the </model-configuration> or </pool-configuration> line), add the following:

<ws-config>

<ws-namespace>urn:xmlns:my-namespace</ws-namespace>

</ws-config>

where my-namespace is the desired custom target namespace.

For complete deployment descriptor XML examples, see http://docs2.attachmate.com/verastream/vhi/7.7/en/topic/com.attachmate.vhi.help/html/reference/deploy_descriptor.xhtml.

Modify plugin-cfg.xml File

In versions 7.5 SP1 through 7.6 SP1, to set a model- or pool-specific custom namespace, complete the following steps:

  1. Edit the plugin-cfg.xml file located in the %VHI_ROOT%/sesssrvr/services/ws/META-INF directory.
  2. Before the </properties> line, add one or more lines using the following syntax:
<entry key="model.model-name.namespace">urn:xmlns:my-namespace</entry>

-OR-

<entry key="session.pool-name.namespace">urn:xmlns:my-namespace</entry>

where model-name is the target model, or pool-name is the target pool, and my-namespace is the desired custom target namespace.

  1. After saving changes, restart the session server service as described in Technical Note 10004.

Legacy Web Service Projects

For web service Web Builder projects created in version 6.6 and earlier, and running in a later version, you can add or modify a targetnamespace=<value> line in the project.properties file.

Related:

  • No Related Posts

7021554: Errors in Microsoft Visual Studio When Using Verastream Host Integrator 7.x Web Service

The following errors or warnings may display when you add the Verastream Host Integrator (VHI) web service to your project, or subsequently attempt to build your project.

Warnings When Adding Service Reference

In your Microsoft Visual Studio 2008 or 2010 project using .NET Framework 3.0 or 3.5, after adding a service reference to the VHI web service WSDL, the Error List may display warnings similar to the following:

Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 2 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: lang' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 3 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: space' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 11 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: base' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 12 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: id' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 13 Column: 3

Validation Error: The attributeGroup 'http://www.w3.org/XML/1998/namespace:specialAttrs' has already been declared.



Custom tool warning: The optional WSDL extension element 'UsingAddressing' from namespace 'http://www.w3.org/2006/05/addressing/wsdl' was not handled.

XPath: //wsdl:definitions[@targetNamespace='urn:xmlns:attachmate:vhi-ws:<model or session>:<model name>']/wsdl:binding[@name='<model name>PortBinding']

Errors When Building Project in Visual Studio 2010

In a BizTalk Server 2010 project, after importing a VHI web service as a Service Reference and attempting to build the solution, the Error List may display multiple errors similar to the following:

Node "<Schema>" - Schema reference "http://<hostname>:9680/vhi-ws/<model or session>/<model name>/<file>.xsd" is not a valid reference or does not exist in the current project.

Figure 1. Sample build errors in Microsoft Visual Studio 2010 Error List

Errors When Building Project in Visual Studio 2008

When attempting to compile your project in Visual Studio, the Error List and build output may display multiple errors similar to the following:

error CS0102: The type '<project name>.<service reference name>.<type name>' already contains a definition for '<name>'

error CS0111: Type '<project name>.<service reference name>.<type name>' already defines a member called '<name>' with the same parameter types

Figure 2. Sample build errors in Microsoft Visual Studio 2008 Error List

Error in BizTalk WCF Service Consuming Wizard

If you are attempting to add a Verastream Host Integrator 7.0 web service WSDL to a Microsoft BizTalk Server 2006 R2 or 2009 project using the WCF Adapter, the BizTalk WCF Service Consuming Wizard may display the following error:

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Related:

Re: EDAA REST – Populate Notification OccurredOn relationship…..

$VAR1 = ‘xmlns’;

$VAR2 = ‘http://www.w3.org/2005/Atom‘;

$VAR3 = ‘entries’;

$VAR4 = [

{

‘xmlns$inst’ => ‘http://schemas.emc.com/vs-xml/namespace/Common/1.0‘,

‘content’ => {

‘Time’ => ‘2018-02-21T09:47:45+00:00’,

‘ErrorMessage’ => ‘Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘RequestUri’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/instances/ICS_Notification::NOTIFICATION-MyNotificationNameHere/relationships/OccurredOn‘,

‘Code’ => ‘4009’,

‘Type’ => ‘OPERATION_ERROR’,

‘vsc$displayName’ => ‘Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘CodeString’ => ‘msa.create.related.instance.operation.error’,

‘links’ => [

{

‘rel’ => ‘http://schemas.emc.com/msa/common/reln/type‘,

‘href’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/types/MsaError

}

]

},

‘updated’ => ‘2018-02-21T09:47:45+00:00’,

‘id’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/instances/MsaError::4009‘,

‘title’ => ‘MsaError – Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘xmlns$vsc’ => ‘http://schemas.emc.com/vs-xml/namespace/Common/1.0‘,

‘links’ => [

{

‘rel’ => ‘http://schemas.emc.com/msa/common/reln/type‘,

‘href’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/types/MsaError

}

]

}

];



Related:

Re: Unable to browse buckets on ECS from S3 browser

Can you have a look at this article: https://community.emc.com/docs/DOC-59224

The article above is going directly to an ECS node. You will want to try that first before attempting to use HAProxy. What type of ECS installation is this? Is this an actual ECS appliance or Community Edition? If following the article still doesn’t work, can you run a simple curl command for me and copy/paste the results (example below)?

ben@USENSCHUMBL4C:~$ curl http://10.1.83.51:9020?ping -v

* Rebuilt URL to: http://10.1.83.51:9020/?ping

* Hostname was NOT found in DNS cache

* Trying 10.1.83.51…

* Connected to 10.1.83.51 (10.1.83.51) port 9020 (#0)

> GET /?ping HTTP/1.1

> User-Agent: curl/7.35.0

> Host: 10.1.83.51:9020

> Accept: */*

>

< HTTP/1.1 200 OK

< Date: Mon, 29 Jan 2018 16:17:28 GMT

< Content-Type: application/xml

< Content-Length: 290

<

* Connection #0 to host 10.1.83.51 left intact

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?><PingList xmlns=”http://s3.amazonaws.com/doc/2006-03-01/“><PingItem><Name>LOAD_FACTOR</Name><Value>1</Value></PingItem><PingItem><Name>MAINTENANCE_MODE</Name><Status>OFF</Status><Text>Data Node is Available</Text></PingItem></PingList>

Related:

EDAA REST – Populate Notification OccurredOn relationship…..

$VAR1 = ‘xmlns’;

$VAR2 = ‘http://www.w3.org/2005/Atom‘;

$VAR3 = ‘entries’;

$VAR4 = [

{

‘xmlns$inst’ => ‘http://schemas.emc.com/vs-xml/namespace/Common/1.0‘,

‘content’ => {

‘Time’ => ‘2018-02-21T09:47:45+00:00’,

‘ErrorMessage’ => ‘Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘RequestUri’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/instances/ICS_Notification::NOTIFICATION-MyNotificationNameHere/relationships/OccurredOn‘,

‘Code’ => ‘4009’,

‘Type’ => ‘OPERATION_ERROR’,

‘vsc$displayName’ => ‘Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘CodeString’ => ‘msa.create.related.instance.operation.error’,

‘links’ => [

{

‘rel’ => ‘http://schemas.emc.com/msa/common/reln/type‘,

‘href’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/types/MsaError

}

]

},

‘updated’ => ‘2018-02-21T09:47:45+00:00’,

‘id’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/instances/MsaError::4009‘,

‘title’ => ‘MsaError – Msa Create Related Instance Operation Error. Source: ICS_Notification::NOTIFICATION-MyNotificationNameHere. Relationship: OccurredOn. Caused by: Cannot invoke method indexOf() on null object’,

‘xmlns$vsc’ => ‘http://schemas.emc.com/vs-xml/namespace/Common/1.0‘,

‘links’ => [

{

‘rel’ => ‘http://schemas.emc.com/msa/common/reln/type‘,

‘href’ => ‘http://myServer.bob:8080/smarts-edaa/msa/edaa-oi-01/types/MsaError

}

]

}

];



Related:

XPS 13 9365 – Scripted install of Win10 1709

I need a solution

Has anyone ever pulled off a successful install of Windows 10 1709 on a Dell XPS 13 9365? I can get all the way through “Installing Windows”, then I’m told there’s a problem with my unattend.xml file–although my deployments work just fine otherwise. Here’s the unattend.xml file I’m using…

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>0409:00000409</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
        </component>
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>1</PartitionID>
                    </InstallTo>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/image/index</Key>
                            <Value>3</Value>
                        </MetaData>
                    </InstallFrom>
                </OSImage>
            </ImageInstall>
            <UserData>
                <AcceptEula>true</AcceptEula>
            </UserData>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
                <SkipMachineOOBE>true</SkipMachineOOBE>
                <SkipUserOOBE>true</SkipUserOOBE>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
            </OOBE>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>cABhAHMAcwB3AG8AcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Name>Altiris</Name>
                        <Group>Administrators</Group>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <TimeZone>Eastern Standard Time</TimeZone>
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1</HorizontalResolution>
                <RefreshRate>60</RefreshRate>
                <VerticalResolution>1</VerticalResolution>
            </Display>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>0409:00000409</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1</HorizontalResolution>
                <VerticalResolution>1</VerticalResolution>
                <RefreshRate>60</RefreshRate>
            </Display>
            <ComputerName>%COMPNAME%</ComputerName>
            <ProductKey>NW6C2-QMPVW-D7KKK-3GKT6-VCFB2</ProductKey>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/users/psy-svc-ghost/iso/sw_dvd5_win_pro_ent_edu_n_10_1709_64bit_english_mlf_x21-50143/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
0

Related:

IIB 10.0 – Using ESQL to create xmlsc document with namespace turns attributes into elements

I am using ESQL to create a XMLNSC document that has a namespace. When I do this, attributes are turned into elements causing the xml to be invalid. Below is the code to create the document in ESQL.

BEGIN
DECLARE pendingDownstreamService REFERENCE to Environment.Variables.PENDING_DOWNSTREAM_SERVICES[1];
DECLARE wd NAMESPACE ‘urn:com.workday/bsvc’;
DECLARE employeeIdAsText CHARACTER;
DECLARE employeeIdToStartDate ROW;
DECLARE employeeCount INTEGER 1;

CALL CopyMessageHeaders();
CALL CopyEntireMessage();

SET OutputRoot.XMLNSC.wd:Get_Workers_Request.(XMLNSC.NamespaceDecl)xmlns:”wd” = ‘urn:com.workday/bsvc’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.(XMLNSC.Attribute)wd:version = ‘v26.2’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Response_Group.wd:Include_Employment_Information = ‘true’;

WHILE lastmove(pendingDownstreamService) DO
IF (pendingDownstreamService.EMPLOYEE_ID IS NOT NULL) THEN
SET employeeIdAsText = CAST(pendingDownstreamService.EMPLOYEE_ID AS CHARACTER);
IF (employeeIdToStartDate.{employeeIdAsText} IS NULL) THEN
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference[employeeCount].wd:ID.(XMLNSC.Attribute)wd:type=’Employee_ID’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference[employeeCount].wd:ID VALUE = pendingDownstreamService.EMPLOYEE_ID;

SET employeeIdToStartDate.{employeeIdAsText} = pendingDownstreamService.START_DATE;
SET employeeCount = employeeCount + 1;
END IF;
END IF;

MOVE pendingDownstreamService NEXTSIBLING;
END WHILE;

RETURN TRUE;
END;
![alt text][1]

Attached is the message from the flow recorder. You can see that the Get_Workers_Request element has version as a child element while the esql code adds the version as an attribute. Additionally, the wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference.wd:ID element has type as a child element while the esql adds type as an atttribute. I also don’t see the namespace declaration attribute in the Get_Workers_Request element so I am not sure if that is a problem as well. I would expect to see something like

in the flow recorder.

How can I add attributes to an XMLNSC document when using namespaces?

[1]: /answers/storage/temp/16366-get-workers.png

Related: