Installations & Upgrades
On-Prem versions, updates and configurations when downloading new version, upgrades
- 93 Posts
- 243 Replies
Want to be the first to get our new On-Premises release ?You are invited to play a central role in the SysAid product roadmap by joining the SysAid exclusive Pathfinder Program, you will get to:Be the first to hear about upcoming releases Be the first to test new features and functionality Share your input at the final stages of development for each new release Receive top priority from our Support team during Beta testing periods Enjoy special events such as exclusive roundtablesSign Up Here Hope to see you in IT,Cheers,Maayan
Hello, we have changed our license and received a temporary license. The invoice has been paid, but we have not received a final license. Now our license has expired. How do we get this now, as we know there is a war going on in Israel? And how can I import the license into the system when I get one since we can no longer log in. FYI, our system runs on Linux.Greetings Wolle
Hello there,We are currently running SysAid on Version v21.4.45 b17, and we want to update to the newest version possible (On-Prem).As a result, I have several questions in mind:While reading through the articles, I came across information stating that I cannot upgrade more than two versions at a time. The issue is that we plan to utilize a completely new VM and Database for the new version. Does this restriction still apply in this case?Furthermore, I am curious about whether we need new licenses for the updated version.Lastly, I am interested in knowing if it's possible to migrate the old tickets that are still active to the new database.Thank you for your assistance.Kind regardsPeter
Hello, I was trying to setup a docker installation on my Centos 8 distro. After following the instructions: - Download the zip - Copy the activation.xml in current dir - python3 SysAid.py install I opted for the MSSql installation When I view the logs after installation (docker logs -f sysaid_sysaid_1), I see the following in the logs: Error while checking connection: Exception while checking configuration: No suitable driver found for jdbc:jtds:sqlserver://mssql/sysaid It seems the JTDS driver is not incuded in the image (sysaid/sysaid_server_linux:20.3.64_12) Any help would be appreciated.
At our site, we have student laptops that are managed remotely using Microsoft InTune. I have the ability to deploy an EXE or MSI program from within the Intune portal. I would like to deploy the SysAid agent MSI this way, is there a way to do this? There is an option for "command-line arguments" from within InTune, does anyone know the command-line switches to use for (Account, SysAid URL, Serial Number, RDS Name, RDS URL)?
Our company utilizes SysAid Cloud. There is an onprem assisting server from which RDS runs and SysAid Agent is pushed out. It has been installing version 188.8.131.52 on new computers without any prior installation. The other 240 computers are running the same version 184.108.40.206 , that they have been running for the last 2 ½ years. How do I get the old agent replaced with the new agent on these endpoints. The assisting server has the new version.
Hello Long time reader first time poster so bear with me. In my environment there is a legal need to scan every incoming and outgoing connection using our firewall (fortigate - deep ssl ) . The only functionality that is broken is no mail fetching due to ssl mismatch. So my real question is : does the platform use different keystone than windows server root authority for outgoing connections ? I need to place my certificate somewhere, but all my tries were failed to say the least. Any ideas fellow sysaiders ?(Have searched the docs , forums, to N/A) Thank you
I will be deploying our new SysAid agent soon and some of my users are part of a Windows Remote Desktop Server environment. Do I just follow the standard steps when installing software into that environment? Is there anything that I need to be aware of as far as possible issues go?
Hello, i’m working with sysadid trial enterprise edition v22.4.45.b2I have a domain administrator credential saved wich seems fine , as I see domain OU, sub.OU, etc. imported, but that same credential seems invalid when trying network scan . I always get “invalid domain administrator credentials” scaning assets on domain.I’ve tried with another valid admin credential but it doesnt work. I get same message.Any idea?Thanks, in advance.
The Agent is installed normally on the client machine, Java is updated and the operating system is updated, but the machine is not registered in the Sysaid console, in the Assets list. The following is the Log Record:>03/06/23 12:57:41:570 [P] SysAidSM::SysAidSWService::OnStart SysAid Agent service started>03/06/23 12:57:43:800 [W] RegWrapper::GetValueEX Warning: Failed to get registry key: SOFTWARE:SysAid:InstalledProducts:SysAid Key: AgentSettingsID System error: 2Failed to register Agent .
We switched from LDAP to Azure auth for our users so now the password reset services screen is no longer working.How do I remove that from the windows 10 login screen? Install method:SysAidAgent.exe /VERYSILENT /URL https://www.web.site /account AccountName /serial SerialNumber /install once /AllowRemoteControl Y /SubmitSRShortcut "Help Desk" /Interval 30 /ConfirmRC Y /RandomMachineID N /AllowSubmitSR Y /LogLevel 3 /ENABLESYSAIDPS Y is it as simple as switching /ENABLESYSAIDPS Y to /ENABLESYSAIDPS N
Please help. I need help configuring SysAid On Prem (ver 22.1.65).I need to configure SMS texting using AWS SNS service. Note, I’ve successfully sent verification text from AWS SNS configuration page to my cell phones (2 different phones). I have AWS account, SNS is configured in Sandbox, I have setup access and secret keys, etc. The dialog below, if set to Amazon Web Services SNS, does not permit me to change the Mobile Originated, Gateway ID, User Name, Password or SMS Protocol fields. The Sender ID is optional and not supported in the US (as I understand it). However, I did try it with a Sender ID that I setup in AWS.I feel as if SysAid isn’t working correctly. See screenshot below:
Has anyone successfully found a way to auto-populate the MacOS sysaid settings with the appropriate URL, ID, and Serial? I have this setup with the Windows MSI configuration, but would like to add this to my workflow for Mac onboarding as well. My workflow treats SysAid as one of many packages installed during onboarding, so I would much rather have this setup as opposed to the SysAid discovery server setup. That seems like another core service to maintain and therefore not the streamlined approach I would prefer.
We plan to do an in place upgrade of our on premise SysAid server. This would be from Windows Server 2012 Standard (x64) to Windows Server 2016 Standard (x64). We have successfully done this on other servers.Other than having VM snapshots and SQL backups for a recovery point and stopping the services, are there any other recommendations or tips for SysAid?
Hi Community, I’ve tried to install sysaid agent, but the computer didn’t show up on sysaid asset lists. The log says the agent shut down. Anyone know how to solve this problem?Here is the log : The current agent version 220.127.116.110/20/22 16:14:28:452 [P] VideoRecordingSettings::ReadVideoRecordingSettingsFromConfigFile The video ticket is enabled10/20/22 16:14:28:494 [P] VideoRecordingDownloadManager::IsNeedToDownloadVideoEncoder The video encoder file exists and ready to use10/20/22 16:14:29:909 [P] AgentStartupHandler::Init Start to init AgentStartupHandler10/20/22 16:14:29:993 [P] AiHandler::Init Start to init AgentStartupHandler10/20/22 16:14:30:653 [P] TeamViewerSessionManager::IsInstalledBySysaid The TeamViewer is not installed by SysAid10/20/22 16:14:30:655 [P] TeamViewerSessionManager::StopTeamViewerService The TeamViewer not installed by SysAid10/20/22 16:14:30:676 [P] AgentStartupHandler::Stop START: stop Agent startup handler10/20/22 16:14:30:677 [P] AgentStartupHandler::St
Login to the community
Login with SSOLogin with oauth
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.