Tag: Windows Task Scheduler

Condition for triggering warning message “XML Security checks can not be performed, once an XML message is found not wellformed.”

Citrix Leave a comment

ADC throws this warning when XMLFormatAction is set to non-block for the first time

XMLFormatAction

One or more XML Format actions. Available settings function as follows:

Block – Block connections that violate this security check.

Log – Log violations of this security check.

Stats – Generate statistics for this security check.

None – Disable all actions for this security check.

1. set to block for the first time, no warning message

> rm appfw profile appfw_test

Done

> add appfw profile appfw_test -rfcprofile APPFW_RFC_BYPASS -type XML HTML -XMLFormatAction block

Done

2. set to values inlcude block

> rm appfw profile appfw_test

Done

> add appfw profile appfw_test -rfcprofile APPFW_RFC_BYPASS -type XML HTML -XMLFormatAction block log stats

Done

3. set it to non block at the first time, warning message displays

> rm appfw profile appfw_test

Done

> add appfw profile appfw_test -rfcprofile APPFW_RFC_BYPASS -type XML HTML -XMLFormatAction log

Warning: XML Security checks can not be performed, once an XML message is found not wellformed.

Done

> rm appfw profile appfw_test

Done

> add appfw profile appfw_test -rfcprofile APPFW_RFC_BYPASS -type XML HTML -XMLFormatAction stats

Warning: XML Security checks can not be performed, once an XML message is found not wellformed.

Done

4. set to log(non block) at the first time, the warning message display, but no warning at the later setting

> rm appfw profile appfw_test

Done

> add appfw profile appfw_test -rfcprofile APPFW_RFC_BYPASS -type XML HTML -XMLFormatAction log

Warning: XML Security checks can not be performed, once an XML message is found not wellformed.

Done

> set appfw profile appfw_test -XMLFormatAction stats

Done

Related:

  • No Related Posts

Error: “You cannot add apps at this time” on Receiver StoreFront

Citrix Leave a comment

Cause 1

StoreFront server is unable to resolve the name of the XML server(s) listed under Manage Server Farms.

User-added image

The following error message is recorded on StoreFront server under Event Viewer > Applications and Security logs > Citrix Delivery Services:

Log Name: Citrix Delivery ServicesSource: WebApplicationDate: <Date>Event ID: 0Task Category: (12346)Level: ErrorKeywords: ClassicUser: N/AComputer: ftlvstorefront.amc.ctxDescription:

The server name ftlvxa.amc.ctxcannot be resolved. The specified Citrix XML Service could not be contacted and has been temporarily removed from the list of active services.

Cause 2

StoreFront server is unable to contact the XML server(s) using the specified XML port number under Manage Server Farms.

User-added image

The following error message is recorded on StoreFront server under Event Viewer > Applications and Security logs > Citrix Delivery Services:

Log Name: Citrix Delivery ServicesSource: WebApplicationDate: <Date>Event ID: 0Task Category: (12346)Level: ErrorKeywords: ClassicUser: N/AComputer: ftlvstorefront.amc.ctxDescription:

An error occurred while attempting to connect to the server ftlvxa45.amc.ctx on port 81. Verify that the Citrix XML Service is running and is using the correct port. If the XML Service is configured to share ports with Microsoft Internet Information Services (IIS), verify that IIS is running. This message was reported from the XML Service at address. The specified Citrix XML Service could not be contacted and has been temporarily removed from the list of active services.

Cause 3

If using HTTPS or SSL Relay as the transport type, StoreFront Services server is unable to contact the XML server(s) using Secure Socket Layer (SSL).

Example of SSL Relay configuration

User-added image

The following error message is recorded on StoreFront server under Event Viewer > Applications and Security logs > Citrix Delivery Services:

Log Name: Citrix Delivery ServicesSource: WebApplicationDate: <Date>Event ID: 0Task Category: (12346)Level: ErrorKeywords: ClassicUser: N/AComputer: ftlvstorefront.amc.ctxDescription:

An SSL connection could not be established: You have not chosen to trust the issuer of the server’s security certificate, amc-FTLVAMCDC-CA. This message was reported from the Citrix XML Service at address. The specified Citrix XML Service could not be contacted and has been temporarily removed from the list of active services.

Cause 4

Third-party network monitoring solutions (for example: firewalls, Intrusion Detection Systems (IDS), antivirus) might be blocking the XML traffic between StoreFront Services and the XML server(s).

Related:

  • No Related Posts

Error Message: Cannot Start Desktop “[DesktopName]” When Trying to Launch a Desktop VDA

Citrix Leave a comment
Open an RDP connection to the Desktop VDA that cannot be launched and check if there is another existing connected/disconnected session in the Task manager. If that is the case then logoff the session and try to launch the published Desktop again.

Note: If the session cannot be logged of from the Task Manager, that probably is because it is an administrator account. Administrator accounts cannot be logged off from the Task Manager. In that case try to contact the person who owns the administrator account and request to logoff. Otherwise, proceed to reboot the host. Then try to launch the published Desktop again.

Related:

  • No Related Posts

“You must use a smart card to sign in” is seen starting a published application on Windows 2016.

Citrix Leave a comment
Users authenticate with usernamepassword to Storefront.

However it is desired to only allow smart card logon on certain VDAs in the environment .

Below GPO setting is enabled

“Interactive logon: Require smart card” located in Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesSecurity Options.

On a Windws 2012 R2 VDA this works as designed .

After clicking OK the follwing logon screen is displayed where a smart card tile is visible to allow smart card logon.


However on Windows 2016 after clicking on OK the session disappears and no logon screen appears.

issue only affects published applications and not published applications.

Related:

ShareFile Migration Tool – Manage Schedules

Citrix Leave a comment

Manage Schedules:

Schedules allow you to choose when transfers are to be run. Admin can use this option to run migrations at times outside of peak usage hours.

Created schedules will be listed in this menu. Click Create New Schedule to make a new one.

Admin can View, Edit or Delete the schedules created using the options provided.

User-added image

NOTE: Large data migration can be handled in better ways using Scheduler. We can schedule transfers outside of peak hours for max bandwidth and speed.

After the user creates a scheduler, the schedules should reflect correctly in Task Scheduler.

Make sure correct details have been added to task scheduler. When there are multiple slots selected, multiple instances should be added in Task Scheduler. Task Scheduler on that machine triggers the event to start migration tool and any migration scheduled in that time frame gets started.

Note: It is required that task scheduler should be working seamlessly on the machine where the tool is being run. And it is required that the user who scheduled the migration should be logged in. If User is not logged in, migration would not be initiated in that specific time slot.




ShareFile-induced Transfer Pause

In the unlikely event of the transfer causing too much traffic on the ShareFile infrastructure, ShareFile may pause the transfer. The Migration Tool will continuously attempt to resume transfer during this time. A warning message will be presented at the bottom of the transferring screen. The user will be unable to manually un-pause the transfer, but can cancel the transfer if desired.

If the number of retries exceeds 48, please contact ShareFile Support.

If the user receives the warning message: “Your account is currently not available to perform transfers”, the ShareFile-induced pause may still be enabled. The user can either wait for this to be resolved or try again later by closing and relaunching the application.

Related:

Naming a windows 10 computer post-image

Symantec Community Leave a comment
I need a solution

Does anyone know if Symnatec might add a task specifically to name a computer with a promt for the end-user? I currently use a powershell script that prompts the end-user to name the computer. Lately, my current windows 10 image of build 1903 has been initiating the altiris agent before my admin account automatically logs into the desktop. The result here is the script will run before-hand and fail. My image job process does the following:

1. Deploy image

2. reboot to production

3. Run windows 10 application job

Step 3 should not start until the administrator account logs in automatically and the desktop is on the screen (this has been working great for years) just lately this issue began. I was thinking instead of a script, does or would Symantec have a speciifc task to prompt for a computer name? I checked out Apply System Configuration’ but the options look like the naming needs to be predefined.

SCCM for example uses a variable OSDCompterName intheir task sequence that prompts the end-user at the start of the imaging job and applies the name into the OS sometime during their imaging process.

0

Related: