DJ-1701

I don't understand how... one day there were just there... Originally when I setup the Primary school, you had to select how many accounts you wish to have, at the great price of £0.00. So we went for: Office 365 A1 for faculty 50 Office 365 A1 for students 15 About a year after that, Office 365 A1 Plus for faculty turned up with unlimited licenses. So... and I started switching over the faculty to these licenses. Office 365 A1 Plus for students appeared with unlimited licenses. Other than that during this time we also did get an EES-OVS agreement, and activated our Software Assurance, but I don't think that had any bearing... could be wrong though.

Well, I believe there is a buyout clause if you no longer want to go ahead with the scheme. Something like needing to order a certain number of perpetual licenses based on your FTE count. Anyway the licensing does cover more than just the Windows license and your ability to upgrade Windows to the latest version (so you can work on Windows 10, as Windows 7 is End of Support January 14, 2020), it also allows you the latest Microsoft Office and Client Access Licensing to your Servers.

I saw that... we need an autocomplete for @'s.

... quietly simmering?

BGInfo on wallpaper with big text stating machine is a security risk, login script to bring up error message stating machine is at risk and some software will not work. It might be worth installing Firefox though and seeing if that works... even if it doesn't work, apparently that will at least have some security patches until June 2018 (source: Which Browser Is Most Secure on Your Old Windows XP System?).

Word to the wise... tiledatalayer has become deprecated. https://4sysops.com/archives/roaming-profiles-and-start-tiles-tiledatalayer-in-the-windows-10-1703-creators-update/#deprecated-tiledatalayer-model I used to copy this folder over directly from a user I configured to the default profile, but that no longer works in 1709 at least.

I think there is something to releasing all that tensed up energy the way you do in metal, certainly a satisfaction in hearing it. I was listening to some of his music during the Summer holidays, stumbled upon some of his covers by suggested videos on YouTube... brilliant.

How could anyone turn down Hobnobs.

Can't say I blame you... long gone are the days of their old motto 'Don't be evil'... if they ever did comply with it.

http://www.edugeek.net/forums/enterprise-software/205256-sccm-deploying-solus-3-sims-net.html#post1758080 Due to strange issues pushing out the Solus agent from the Solus server, I have decided to take a leaf out of @Boredguy's book and not bother pushing out from the server console... but instead deploy it with a script which records the GUID in a CSV file for easy reinstallation. Notes: The following is setup for a 64 Bit Windows OSes, but can be modified to work with 32 Bit by adding a few lines of code and the installer. If you can not find a copy of the Solus agent on your server, you can go into Solus Deployment Service, click Settings, SOLUS3, SOLUS, Export agent installer. Let's get started... In a new folder on your software deployment server share, create a folder called Solus and copy the following items: Solus3.Keys.DeploymentService.Public.xml (From the Solus Server) SOLUS3AgentInstaller_x64.msi (From the Solus Server) Agents.csv (new blank file, needs user write permissions to this file only) SolusInstaller.ps1 (i.e. coding below). Coding note: 1) Replace \\DEPLOYMENT-SERVER-HERE\SHARE-HERE$ with your Deployment share that holds the Solus folder you created. 2) Replace SOLUS-SERVER-HERE with your Solus Server Name. PowerShell code for SolusInstaller.ps1: $Found=$false $CSV = "\\DEPLOYMENT-SERVER-HERE\SHARE-HERE$\Solus\Agents.csv" $SolusAgentDataList=IMPORT-CSV $CSV -Header ("ID","Name") $GUID=[system.GUID]::NewGuid().ToString() $ComputerName = (Get-Childitem env:computername).Value ForEach ($SolusAgentDataItem in $SolusAgentDataList) { If ($SolusAgentDataItem.Name -eq $ComputerName) { $Found=$true $GUID=$SolusAgentDataItem.ID } } If (!$Found) { Add-Content $CSV "$GUID,$ComputerName`n" } &msiexec.exe /i `"\\DEPLOYMENT-SERVER-HERE\SHARE-HERE$\Solus\SOLUS3AgentInstaller_x64.msi`" AGENTSERVICEADDRESS=`"net.tcp://localhost:52966`" AGENTID=$GUID DEPLOYMENTSERVERADDRESS=`"net.tcp://SOLUS-SERVER-HERE:52965`" RSAKEYPATH=`"\\DEPLOYMENT-SERVER-HERE\SHARE-HERE$\Solus`" /qn /l*v C:\solus.log Start-Sleep -s 5 To ensure you reuse the same GUID, and get your SIMS/FMS/Discover automatically reinstalled when you rebuild your PC, you can get existing Solus agent GUIDs by looking at AGENTID located in HKEY_LOCAL_MACHINE\SOFTWARE\CCS\SOLUS3\Agent and adding manually to the CSV file in the format. 01234567-89ab-cdef-0123-456789abcdef,Computer-Name-Here with a new line at the end. When the script is run on any machine with a computer name that hasn't been recorded in the CSV file, as long as you have given the Installer write permissions to the CSV file, a new GUID and the computer name will be added into the CSV file. You can then go on Solus and assigned SIMS/FMS/Discover to the Agent. When the script is run on any machine with a computer name that IS recorded in the CSV file, the GUID is picked up from the CSV file and Solus will install with the software you had previously specified.

As Solus can't be bothered to push the client out correctly... I have decided to take a leaf out of @Boredguy's book and not bother pushing out from the server console... but instead deploy it with a script which records the GUID in a CSV file for easy reinstallation. http://www.edugeek.net/blogs/dj-1701/2317-deploying-solus-via-powershell-script.html

Yes, a few times in both schools. Would use again.

Unfortunately that isn't the case either. Only one DNS record per machine and they are correct.

Good thought, but unfortunately not. In continuing experiments, I have just tested a manual installation of the latest version of Solus on a new machine and that works too.

I've noticed at the Primary that Solus is refusing to deploy or update when pushing out via the SIMS server. This has been working fine until recently and was wondering if anyone else has been having an issue with it? After adding a computer to the server the Agent window states it is copying the agent installer files, and then fails to communicate, even though the computer is accessible from the server with those credentials. I have managed to install the client by manually installing it from the client directory originally setup by Capita (all be it an older version of Solus), but then it doesn't update from the server (SIMS and FMS deploy fine though). Another strange thing is that I had to open 8080 on the server for the clients to access the document server so reports can run, which didn't need this setting before.

Not another one...

Well they worry about children more in Germany... because... they're kinder.

Like pancakes into a blackhole...

Well with some of the cast members passing beyond the rim, it is hard to make new series now.

Errrr... you do have Laws since at least 2003 being in line and part of the WTO. Even if you didn't, I am sure the Terms and Conditions of use would be violated and a legal issue.

That does look impressive... but as so many people code differently and don’t comment their code, it might drive me crazy bug checking.

That's a tad harsh... some of your species is alright... those you have elected though *shudders*.

Ha, these so-called compasses don't even work... I hear they just use the sharp bit to force people into their sadistic spherical cult.

Don't think I will be able to make this one, but have a good time all.