New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VDA Configuration results in Citrix Desktopservice as Disabled #70

Closed
madrianr opened this Issue Sep 28, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@madrianr
Copy link

madrianr commented Sep 28, 2018

Describe the bug
If I activate the Delay Citrix Desktop Service then after runnig BIS-F the Citrix Desktopservice as Disabled...

Screenshots
unbenannt1
unbenannt2

Desktop (please complete the following information):

  • OS: Windows 10 1803 x64
@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator

matthias-schlimm commented Sep 28, 2018

RTFM :-)

https://edocs.eucweb.com/docs/bis-f-6-1-0/configure/citrix/

Delay Citrix Desktop Service:
The Citrix Desktop Service controls the registration state through the Citrix Controller. In some circumstances, this service has successfull registered the VM and the user can logged on to this, through Receiver/StoreFront. In the Backend some depend actions like Workspace Environment Agent, Group Policies, App-V Client and someone else are not completed with their own task. If you enable this policy the Citrix Destop Service would be started first, if the BIS-F personalization is finished.

Note: If you has the Device personalization configured to skip it on all DiskModes or on private Mode only, the Citrix Desktop Service would also be started.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator

matthias-schlimm commented Sep 28, 2018

any questions ? otherwise I will close it

@madrianr

This comment has been minimized.

Copy link
Author

madrianr commented Sep 28, 2018

First it is not fine to see RTFM :-(

I'm new to BIS-F and it seems that I do something wrong - so it would be nice to Point me in the Right direction - what I'm missing?

robert

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator

matthias-schlimm commented Sep 28, 2018

no worries ...

If you enable this policy, BIS-F disable the service during sealing and on startup, the BIS-F scheduled task starts the Desktop Service at the end of the BIS-F personalization.

@madrianr

This comment has been minimized.

Copy link
Author

madrianr commented Sep 28, 2018

what is the BIS-F scheduled task - do you mean the Service should be startet after sealing?

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator

matthias-schlimm commented Sep 28, 2018

The BIS-F scheduled task is creating during sealing. It's needed on startup and processes all scripts in the personalization folder

https://edocs.eucweb.com/docs/bis-f-6-1-0/flow-diagramm/personalization-system/

@madrianr madrianr closed this Sep 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment