On a few new Win 2012 / Win 2016 systems I’ve setup on my home lab over the past week , I’ve noted various error messages on attempting the following simple Powershell cmdlet based process which you would use to export the config of a working StoreFront server to a new StoreFront server.
Citrix details the process here
1 – Open an elevated Powershell session on your existing StoreFront server that’s fully setup
2 – Add-PSSnapin Citrix*
3 – . “C:\Program Files\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1” (note the “.” at the beginning”
4 – Export-STFConfiguration -TargetFolder “c:\StoreFrontConfigs” -ZipFileName Source -NoEncryption
Output of the various config pieces being written to the screen will be shown. With the above commands completed, you would then logon to your second server to import the newly created config where you would run through the following:
1 – Copy over the .zip created in step 4 to a local folder on the new server
2 – Open an elevated powershell session
3 – Add-PSSnapin Citrix*
4 – . “C:\Program Files\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1”
5 – Run Import-STFConfiguration -ConfigurationZip “Path to .zip”
That SHOULD be it, right? NOPE! On my test servers at home Win 2012 R2/ Storefront 3.9 and Win 2016 / StoreFront 220.127.116.11 running the import-STFConfiguration resulted in the following cryptic error:
Import-STFConfiguration : An error occurred configuring StoreFront diagnostics. The property ‘instance’ cannot be
found on this object. Verify that the property exists.
At line:1 char:1
+ Import-STFConfiguration -ConfigurationZip C:\StoreFrontConfigs\Source …
+ CategoryInfo : NotSpecified: (:) [Import-STFConfiguration], Exception
+ FullyQualifiedErrorId : System.Management.Automation.CmdletInvocationException,Citrix.StoreFront.ImportConfiguration
Now, I can still setup the 2nd server by using the Studio method ; where I create a server group between the existing and new server, and sync the config. However, shouldn’t the Import-STFConfiguration cmdlet do the trick? Anyone else seen this and no of a fix? The Citrix forums have a few posts, but nothing definitive.
My current lab environment supports a few goals:
- Stay sharp with Microsoft active directory and group policy
- Keep up to date with windows server versions: 2003, 2008, 2012R2, 2016 > beyond
- Keep up to date with the windows desktop OS family
- Keep my hardware skills sharp by continuing to build my own desktops and servers
- Keep up to date with Citrix XenApp/Desktop suite releases: in 2017 alone, I ran 7.11, 7.12, 7.13, and 7.15 LTSR – a lot!
- Use Powershell for automating routine tasks
- Enable quick recovery from hardware/software failure through OS virtualization
- Prep for certification
All of the above has been achievable using two full size ATX based towers, and one SFF – a Gigabyte Brix
- ATX Tower 1 runs server 2016 and Hyper-V – VMs run SQL , file a backup AD controller
- ATX Tower 2 runs ESXi – Citrix StoreFront, Citrix desktop controller, session hosts and MCS
- The Gigabyte brix is used for appliance functions – vCenter and active directory primary
DRP is covered by a multi-port UPS and USB 3 10 TB HDD
Each year, (and not always @ x-mas) I have the exact same hardware purchase temptations:
- A synology NAS unit for backup
- An off-lease Dell R series or HP/Cisco equivalent
However, I always defer to the next year, when I’ve got a newer apartment w. more room 😉
The 3 unit setup covers my needs for 2017 so far, but i’ve become interested in VMWARE VCP-DCV certification recently, in doing so, I would more than likely go to a 4-host setup to enable VSAN. So, purchasing a 4th ATX or MATX based tower will more than likely occur sometime i the next 4-6 months. I’m looking at an Intel Coffee lake based rig, as they traditionally feature better ESXi support.
In my previous job, my exposure to Citrix imaging solutions was limited to PVS. So, over the past few days, I’ve been going through the process of setting up MCS in my home lab.
To be honest, it’s a pretty great out-of-the-box experience. PVS is a lot of work to setup / maintain, man! 🙂
Anyway, I was able to create a nice simple master image for my MCS machine catalog, and tested out basic functionality today, however, I ran into a Google Chrome + Citrix gotcha!
I was logged into a long-build (non-MCS) server VDA session on my home lab hardware, then opened a new MCS VDA server session, all apps opened fine on the 2nd session, but chrome!
I had enabled Chrome folder redirection to cut down on Citrix UPM/roaming profile size, however, when you enable Chrome %AppData% redirection, you can only have one session per user opened at a time!
For reference, the *gotcha* is listed on the Google Chrome product forums, here:
The fix was simple, exit Chrome on session 1, I was then able to open it on Session 2.
I’ve had Sonos gear for about 5 years now. 4 units, great little speakers – when they work!
Case in point, I disabled SMB v1 on my win 2016 hyper-v based file server this weekend, only to discover that the default (as in only) SMB format that Sonos supports to enumerate/connect to windows shares is SMB v1. Yikes!
It’s noted here:
I found it while skimming through 100’s of posts over the past few years on the Sonos customer support forums.
I was about to take to Twitter-bird to chide Sonos for this over-sight, when I noted MSFT Ned Pyle from Microsoft already had!
He’s got this post from last year on the topic
Regardless, I hope Sonos add SMB v2 or v3 support to their units soon. SMB v1 needs to die!
I’m going through a multi-stage upgrade to my aged home lab hardware, part 1 includes mostly storage items, 4 of those items arrived today!
1x WD Red 7200 RDP 10 TB HDD for file server
1x mATA to M.2 HDD adapter for file server
1TB Samsung 960 Pro M.2 HDD
2x 8 GB DDR3l SODIMMS for Gigabyte Brix (ESXi host)
I’m working out a plan to get the new items installed with little to now down time. i’ll post my plan soon!