-
Posts
960 -
Joined
-
Last visited
-
Days Won
23
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Rob Zylowski
-
-
DHCP is required or the packaging machine will not get an IP address
-
Does the packaging machine get the correct vlan when its created? And does that vlan have dhcp?
-
-
You definitely used a template and not a VM correct? A VM would not work right.
-
You need to create a vmware template with no disks that has the settings you want then assign thar in your connector config. Its best to use a one of your gold image if you have it.
-
This is expected behavior for non-persistent machines. Its nothing to do wiht app layering and would be the same for pvs, mcs or any cloning technology that does not run sysprep during machine creation. The Domain Machine Account will be unique but not the machine guid
- 1
-
Hi James,
Just finished testing layering studio. I was able to get it to work in an app layer. I noticed that the version i was using (CVAD 2308) had new C++ libraries and .net 4.8 so I went back to my OS layer (on server 2016) and added them there forst before creating the layer. I had a little weirdness when rebooting the vm after the install i had to reset it as it got stuvk rebooting but then i just loged in again, ran ngen and rebooted one more time and the second reboot was fine.
You didnt mention the issues you ran into can you explain them.
-
Never tried it but i can. It might have to go into the Platform layer since its Citrix software.
What OS are you using?
-
If you check the master image and look in the c:\windows\setup\kmsdir folder is there a file called runato_done? If so delete it before shutting down. That is a flag file that says dont run activation its already been run.
The SetKMSVersion.hta uses the windows caption to find the version of the OS you are using then it creates the runato.cmd wiht the correct activation script for that version. It does need to be run as administrator to wrote to the kmsdir folder. If its not on you master image then check your os layer for it the runipkato.cmd and make sure its calling the correct script version.
As for image prep failing that often has to do wiht the time on the image prep machine being way off. But the way we do activation using scripting in App Layering you can disabled image prep if you want to in MCS. If you do find that its a time issue that is normally fixed by using a hypervisor template when you publish your image based on a virtual machine that has all the right settings and that has been starting and running the correct time zone in windows so that that setting gets stored in the virtual bios.
-
Update on this topic. I just tested and got 2.1 to work but right now you have to install it in the OS layer. I hope at some point this can changes but it is a universal apps and those nee to be in the OS layer. I will repost if anything changes with regards to this.
-
No when you check the box the appliance will rewrite the json files on the EL share and that setting will eb added. The next time the layer is used it will be loaded before logon. All published apps have to be set to compatibility mode.
-
Are you using a custom role for permissions or an Admin account? If custom and you can try with a full admin just to rule out permissions as the issue.
-
You should be creating a new packaging (not publishing) platform layer is that what you are doing?
Is vmware tools not in your os layer?
What is the error you see in View?
I havent done this in a while but i would expect it to work fine
-
no worries glad you figured it out
-
It would have to be another layer that is not common between them and that has a higher priority than your fslogix layer.
-
Sounds like it was changed in the platform layer. Add a. Version to that and check. Buy yes you only need it if you enable elastic layering
-
No determining what's going in the pvs cache id always difficult, But its pretty weird its only one user but there are a few folders we dont put in the user layer and maybe this user has added something to their user layer that is affecting those folders.
-
So your issue is that the pvs cache runs out of space?
You right that is strange as almost al writes after the user layer is attached should be going to the user layer.
I think you will need a case for this one.
-
Hi David,
Did this start happening after an event like an upgrade or a failure to create a layer?
Do you have a backup of the appliance from before you had this issue?
-
It cant but its an hta that just runs vbscript so you coulf just copy the code.
-
It cant but its an hta that just runs vbscript so you coulf just copy the code.
- 1
-
When you said 8016 was open that was from appliance to agent ?
You also need these
App Layering Source App Layering Destination Activity Protocol Ports
Agent on Hyper-V serverAppliance Disk download TCP3012 (HTTP), 3512 (HTTPS)
Agent on Hyper-V serverAppliance Disk upload TCP3015 (HTTP), 3515 (HTTPS)
Agent Appliance Log deliveries from agent TCP8787
User Interface Appliance 3512
see
https://docs.citrix.com/en-us/citrix-app-layering/4/manage/firewall-ports.html
But it seems like the appliance cant talk back to the aent on 8016 according to the error you posted.
-
The error indicates you can get to the appliance so its timing out. Is there a proxy configured on the hyperv host? You will probably have to
On 10/27/2023 at 2:55 PM, Chris Bondy1709160344 said:I am chatting wiht engineering. They asked:
Does the CreateInfrastructureCommand show up in the web.log on the ELM?
If you download the log bundle from the elm you will find the web.log
-
This is something we are working on sometimes the file server is too busy to mount the layers. No ETA yet.
Platform Layer: The compositing engine failed to initialize after '00:20:00'
in App Layering 4.x
Posted
I think you may also have a case i saw this query on our internal slack this morning but i think you can use a VMware template to define a mac address directly. Then use that mac address for a reservation. The key here is you will need different templates wiht different mac addresses and then different connector configs to support packaging more than one layer at a time. But it you should be able to get that to work.