https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
d
Thx Julian. I see the same error at the moment 😵
l
Me too. Had to run a manual install. I was more interested in testing features.
j
Sitting here since the morning and trying stuff 😡 Nice christmas present from Citrix
l
Now.... That was something I was not willing to do. Lol. You are a bit of an IT soldier Julian ;-)
s
I’m not having any issues with unattended install
j
Can you share the part of your script where you are creating the site database? "New-XDDatabase -AdminAddress $ComputerName -SiteName $SiteName -DataStore Site -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName_Site -ErrorAction Stop"
@Leee Jeffries: no more than you 😉
s
Thanks for this @Julian Mooren need and will test, only upgrade has been did so far.. no issue at this point in time.
s
New-XDDatabase -AdminAddress $target -SiteName $SiteName -DataStore Site -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName_Site -DatabaseCredentials $Database_CredObject
Looks like the difference is i'm passing credentials
j
I am not passing the credentials because the service/build user with the SQL rights is doing an auto login and then executing the script.
DatabaseCredentials: The security credentials, in the form of a PSCredential object, that will be used to connect to the SQL Server specified by the DatabaseServer parameter. If this parameter is not provided, then the implicit credentials of the user running the cmdlet are used to connect to the SQL Server.
s
i assume you are rebooting before configuring?
j
Yes + Snapins are registered,
s
i'm using sql 2017 trial
WS2019 also
j
WS2019 + Express 2017 but I guess thats not the problem
s
For my Controller install args, I'm using the following.
"/quiet /configure_firewall /COMPONENTS CONTROLLER,DESKTOPDIRECTOR /IGNORE_HW_CHECK_FAILURE /nosql /noreboot'"
remove the double quotes
Also using XenDesktopServerSetup.exe
j
Same excpect the HW check
$Arguments = "/components controller,desktopstudio /configure_firewall /nosql /noreboot /quiet /logpath ""$LogDir"""
s
you might consider passing the credential just as a test. maybe the bug is in how it assumes the install account's credential?
j
Same error message when passing the credentials
l
My New-XDDatabase is identical to Steve's.
XD install - /quiet /noreboot /configure_firewall
My controller performs all roles.
Can you check your SQL logs to see if the login is successful?
j
SQL Log is empty. Cant see any connection from the controller
j
No problem for me but I always use a credential object even if it is the same as the connected user
j
Question for the people with the error message: Are you using MDT to build the machine? When I interactive execute the script the PowerShell cmdlet is doing its job and creates the site database. It’s just not working during a Task Sequence. Tried with runas and Auto-Login with the service build account.
l
Is it a UAC/execution policy thing. I need to test this. Won't happen for a few days though. Busy busy family things.
j
UAC is disabled/Execution Policy configured to ByPass during deployment. Family goes first 🎄🙂👋🏻
j
Perhaps MDT is using system account. Try to output the whoamis command to check this point. Mery Chrismas !
j
Then I would have had problems with previous deployments as well. As posted on Twitter: Staging a 7.15 CU5 controller is working without any errors. It is not running in the system context 👍🏽
@Deyda, @Leee Jeffries, @Eric: Any Update from your site?
l
Sorry man. Not done anything with it. Been spending plenty of time with the kids. Once I touch anything work related my brain will snap straight back into it.
e
I’m using the script as @Steve Elgan Thinking about it and my recent $env setups, this is most likely a SQL Express issue.
j
Going to deploy with a Standard SQL 2017 server tomorrow. All tests have been done with SQLExpress (Stand-alone Server or Express via CVAD Installer)
l
Can you check your SQL logs and see if login to the server is successful. I have had issues recently with AD accounts in SQL express 2017. Weird issues when migrating citrix DBs for small shops.
j
Started some VMs for deployment last night. Here are the results: • No failed logins because no login is happening at all SQL 2017 and 2017 Express -> No difference • Staging a 1909 Controller is working without any problems -> DB is being created Just 1912 LTSR is throwing the error that there is a problem with the SQL communication
l
Sounds like you have a reproduction for your issue. Time to raise a ticket and get a bug logged. Nice work Julian.
j
I am already in contact with Mandbinder Singh. Keeping you updated. Feels like canary testing 🙈
l
Manual install works. Depends how many people automate.
j
Yes but that should be on of the essential things to test before releasing a CR/LTSR? I don’t want preclude there is an unknown constant in my environment but other people are experiencing the same problem and with the previous releases everything is working as it „should“
l
Yeah true. Throws a spanner in the works for sure.
j
To be continued in 2020... Need to get some things done for the dinner party this evening. Happy New Year Lee 🍀🎉
l
Happy New Year my friend. Enjoy the party!
j
Any update from you guys? Captured a CDF Trace today and send it to Citrix. Did some digging with Procmon today. You clearly can see that the 1912 PowerShell Commandlet ist not even trying to connect to the SQL Server. Working Capture is from a 1909 installation.
I found the reason. Controller is running unattended again!!! 🙂
e
Awaiting your results
j
Post is in the making
s
Thanks so much @Julian Mooren 👍👍👍
j
This was driving me nuts 🙂
s
I can fully imagine...🤜🤛
s
Glad you found it!
✅ 2
l
Nice one dude, great work. #wasntgoingtoletitgo
e
Awesome T/S
4 Views
Open in Slack
PreviousNext
Powered by