Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’)

Try to determine which files are taking up disk space. on Identity disk

For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

The PsExec tool is available for download at this location

http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Follow these steps to access the Identity disk volume on the VDA:

1. Open elevated command prompt <Run as administrator>

2. execute the command under the context of the Local System account via PsExec:

PSEXEC -i -s cmd.exe

This it to access to the junction linked to the Identity Disk volume

3. Navigate to the root of the junction “PersistedData”, and execute the following command:

DIR /O:S /S > C:{location}Out.txt

4. Open out.txt using Notepad or text editor

5. Check the files taking up the disk space.

6. Move the unwanted files to an alternate location or delete them

Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

Related:

  • No Related Posts

Event ID 1023 Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’). VDAs in Delivery Group losing registration with the Delivery Controllers

Try to determine which files are taking up disk space. on Identity disk

For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

The PsExec tool is available for download at this location

http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Follow these steps to access the Identity disk volume on the VDA:

1. Open elevated command prompt <Run as administrator>

2. execute the command under the context of the Local System account via PsExec:

PSEXEC -i -s cmd.exe

This it to access to the junction linked to the Identity Disk volume

3. Navigate to the root of the junction “PersistedData”, and execute the following command:

DIR /O:S /S > C:{location}Out.txt

4. Open out.txt using Notepad or text editor

5. Check the files taking up the disk space.

6. Move the unwanted files to an alternate location or delete them

Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

Related:

  • No Related Posts

Re: The configuration of this client does not support browsing on Red Hat clients

thats what I thought.

so when you choose the folders in Backup and Restore – you get an error correct?

I am the same way NONE of my RH servers quilify for FLR (see below for Limitations)

so I have to backup my Linux VM’s as a vm once a week (so I can rebuild if needed)

and daily I do backups as a physical with the client installed on the server.

File-level restore limitations

The following limitations apply to file-level restore as described in “Restoring specific

folders or files” on page 86:

The following virtual disk configurations are not supported:

• Unformatted disks

• Dynamic disks

• GUID Partition Table (GPT) disks

• Ext4 filesystems

• FAT16 filesystems

• FAT32 filesystems

• Extended partitions (that is, any virtual disk with more than one partition or when

two or more virtual disks are mapped to single partition)

• Encrypted partitions

• Compressed partitions

Symbolic links cannot be restored or browsed

You cannot restore more than 5,000 folders or files in the same restore operation

The following limitations apply to logical volumes managed by Logical Volume

Manager (LVM):

• One Physical Volume (.vmdk) must be mapped to exactly one logical volume

• Only ext2 and ext3 formatting is supported

Related:

  • No Related Posts

7022440: System does not boot any more after extending root filesystem

This document (7022440) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 1 for IBM Z (SLES 12 SP1 s390x)

SUSE Linux Enterprise Server 12 Service Pack 2 for IBM Z (SLES 12 SP2 s390x)

SUSE Linux Enterprise Server 12 Service Pack 2 for IBM Z (SLES 12 SP3 s390x)

Situation

After adding a disk volume to the volume group of the root filesystem, or in case of btrfs, to the root filesystem itself, the root filesystem cannot be mounted on next IPL. Systemd endlessly prints messages similar to A start job is running for dev-disk…ab12cdef.device (60s / no limit).

Resolution

After adding the additional disk and before restarting the system, grub2 and the initrd need be updated so it will set the additional disk volume online. The following commands will do that:

grub2-install

mkinitrd

In case the system was rebooted without recreating the grub2 bootloader and the initrd, the rescue system can be used to fix the issue.

Cause

Grub2 and the initrd will only set disk devices online that are needed to mount the root filesystem to avoid long waiting times when a large amount of disks are visible to the system. Thus, both need to be updated to contain the information that an additional disk is required. This affects only filesystems mandatory to start the installed system, for filesystems that get mounted afterwards this is not necessary.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

Modifying/changing DB2 database paths for CLM

Hi All,

We have CLM server running which is configured using DB2 and WAS on Linux box. There are four mount points created on linux server for database Storage. Now the problem is the storage on this mount points have become full. We cannot increase the disk storage for this mount points due to limitations, however we are planning to move this database locations to new mount points which have more storage. How can we achieve this..? Can we just directly copy the contents from old mount point to new points..?

Thanks,
Kunal

Related:

  • No Related Posts

Error: “1 non-ignorable errors were returned for a Major snapshot.” When Performing a Major Snapshot from XenMobile Mail Manager

When attempting to perform a Major Snapshot from within XenMobile Mail Manager, you find that the process fails with the following error recorded in the log file:

[Warn] EnvironmentBridge.Specialist: Method: TakeSnapshot (HandleEarlyReturn), Environment Id: GUIDID101-101A-101A-101A-ABCDEFG12345, CLR Thread ID:’23’, URI: http://servername/PowerShell?serializationLevel=Full, Exit – SnapshotType: Shallow, SnapshotKind: Major, Connection.Id: abcdefg-1234-4321-aaaa-abc123def456.

The snapshot returned early with a reason of ‘Snapshot errors during mailbox phase’ and a message of ‘1 non-ignorable errors were returned for a Major snapshot. The (####) mailboxes will be discarded.’

Related:

  • No Related Posts

Ghost Client appears to break Sysprep. Machine wont boot.

I need a solution

Ok, so I have a Windows 7 image that has been imaging ok with earlier versions of ghost 3.x  With the last two updates it appears to break sysprep some how.  If the Ghost client is not on the machine, it can sysprep without issue.  Once i deply the agent and attempt a sysprep the machien does the initial sysprep functions but on reboot it will never boot because its like the parftitions are not there.  You get a windows failed to start File:windowssystem32configsystem status 0xc000000f error. You cant boot into anything at this point .  If you boot to a windows 7 iso and select repair it will fix the OS and it is able to boot.  Not a solution for high volume imaging.  When you boot to the ISO and select system recovery options it’ll show that no partitions are found. Its like the boot partition gets corrupted somehow.  Has anyone seen this?  The OS has the default windows Boot partition, the C: drive  and Recovery partition.  I know that if do a clean build of the OS with a single partition then the ghost agent install does not affect the sysprep.  Certainly a strange issue, but would appreciate any input.

So in short – Windows 7 image with the default 3 partitions. Installing the Ghost client and running sysprep breaks the machine. If you leave the Ghost client off, it syspreps successfully.

0

Related:

  • No Related Posts