| Author |
Message |
|
|
Hi heini68,
This text can be edit in the Translation file. Please go to Preferences -> Customize -> Translate
Download the file search for the welcome text and edit it and then upload it to the same location and will take effect on the spot.
Regards,
Eli
|
|
|
Hi Global-ICT,
Here is a text you can add into customize "customized notifications" tab.
#if( ${Status} && ${Status}=="Ready" )
Texts/links that will be shown on notification
#end
Best Regards,
Eli
|
|
|
Hi All,
Here is a great explanation of using the SysAid Assets and the CMDB Module.
Asset licenses will enable automatic auditing and remote control your PC's and servers using an agent.
The SysAid agent will collect all necessary information regarding hardware and software updates and provide monitoring capabilities.
Therefore, when managing workstations and servers, it is recommended to use the agent to maximize your control over your IT environment.
For all the other non-managed assets (ip phones, PDA's, printer and scanner etc.) you can surely use the CMDB module.
*************************************************************
In SysAid Full Edition, the CMDB module can hold an unlimited number of CIs (Configuration Items) of all types: system items, service items, physical items, conceptual items, etc. For each CI SysAid allows more than 250 customizable fields - to fit your exact needs. You can even set different views for each CI type. For Instance, SysAid allows you to see only the relevant fields for 'system item' CIs, while for 'physical items' you can see a whole different set of fields.
The SysAid CMDB maintains a comprehensive list of all types of relationships between your CIs, and helps you predict the influence of changes in your network on future developments and business impacts. Therefore, using the SysAid CMDB may significantly lower your expenses.
Best Regards,
Eli
|
|
|
Hi Xboxkent,
That is correct if you are interested in Beta testing SysAid Server version 6.0 Please go to the following URL http://www.ilient.com/sysaiders.htm to sign up.
Best Regards,
Eli
|
|
|
Hi All,
That correct the SysAid Sever Beta 6.0 is just right around the corner. If you are interesting on Beta Testing it please sign up for Pathfinders on our Website at the following URL http://www.ilient.com/sysaiders.htm.
As a wrong around you can attach the image to a service request and when closing the service request add it as a knowledge base item.
Best Regards,
Eli
|
|
|
Hi Jsin04,
Thanks for the update on the turn out of the SMs great to hear everything is working.
Regards,
Eli
|
|
|
Hi mreyes,
Thanks for letting us know how it turned out after closing the Install shield 09 application.
Best Regards,
Eli
|
|
|
Hello Russ,
Thanks for letting us know that when replacing that the GNU Java, and installed the Tomcat from the web worked out well.
Eli
|
|
|
Hi JeHap,
Please stop your Tomcat and remove the following files from "...\SysAidServer\tomcat\lib" the "activation.jar" and "mail.jar".
Then restart your Tomcat server.
Please let me know if that resolves your issue. If not, or you need further assistance, please don't hesitate to contact us. Your response will be highly appreciated.
Best Regards,
Eli Matoren, MCSE, MCTS, MCITP,
|
|
|
Hi DrRingDing,
In order to install SysAid on (Red Hat) Linux using the embedded Derby database, please follow the instructions below:
1. Install Sun Java JRE 1.5 or a later version. Java is available at http://java.sun.com/
2. Install version 5.5.25 of Tomcat which can be downloaded at http://archive.apache.org/dist/tomcat/tomcat-5/v5.5.25/bin/apache-tomcat-5.5.25.tar.gz.
Make sure to point JRE_HOME to the Sun installation of Java (eg. export JRE_HOME=/usr/java/jdk1.6.0_04).
3. Deploy the sysaid.war file to the Tomcat server. Usually you will just need to copy it to the webapps directory, and Tomcat will automatically deploy it. A sysaid directory tree will be created in the deployed location (default is tomcat/webapps/sysaid). SysAid will now start to work with the derby database. Please make sure to start the Tomcat server before accessing SysAid by running the command ./startup.sh in the bin directory of Tomcat.
4. If you have a license file for the full version, please replace it now at tomcat/webapps/sysaid/WEB-INF/conf/activation.xml and restart the Tomcat server.
5. Start the Tomcat server by running the command ./startup.sh in the bin directory of Tomcat.
6. Access SysAid at http://<host>:<port>/sysaid. The default port for Tomcat is 8080.
7. The main login username / password will be sysaid / changeit .
In order to install SysAid on (Red Hat) Linux using the MySQL database, please follow the instructions below:
1. Install SUN JAVA JRE 1.5 or a later version. Java is available at http://java.sun.com/
2. Install version 5.5.25 of Tomcat which can be downloaded at http://archive.apache.org/dist/tomcat/tomcat-5/v5.5.25/bin/apache-tomcat-5.5.25.tar.gz.
Make sure to point JRE_HOME to the Sun installation of Java (eg. export JRE_HOME=/usr/java/jdk1.6.0_04).
3. Install MySQL version 3.x or 4.0.x database server. MySQL is available in most of the Linux distributions and also available at http://dev.mysql.com/downloads/mysql/4.0.html .
4. Create an empty database in the MySQL server.
5. Deploy the sysaid.war file to the tomcat server. Usually you will just need to copy it to the webapps directory, and Tomcat will automatically deploy it. A sysaid directory tree will be created in the deployed location (default is tomcat/webapps/sysaid).
6. If you have a license file for the full version, please replace it now at tomcat/webapps/sysaid/WEB-INF/conf/activation.xml.
7. Execute the init-sysaid.sh script. The first and only required parameter is the location of the deployed SysAid web application (e.g. ./init-sysaid.sh /usr/local/tomcat/webapps/sysaid ). Follow the instructions in that initialization script.
8. Start the Tomcat server by running the command ./startup.sh in the bin directory of Tomcat.
9.Try to access SysAid at http://<host>:<port>/sysaid. The default port for Tomcat is 8080.
10. The main login username / password will be sysaid / changeit .
Please let me know if that resolves your issue. If not, or you need further assistance, please don't hesitate to contact us. Your response will be highly appreciated.
Best Regards,
Eli Matoren, MCSE, MCTS, MCITP,
|
|
|
Hi MichelleU,
Can you please provide us with a screenshot of your settings in the SysAid Deployment Tool. To further assist you with this issue.
Looking forward to your response.
Eli
|
|
|
Hello All,
Just release the BETA is now available for Windows Server 2008 and Windows 7 at the following URL
Agent Install: http://www.ilient.com/down/SysAidAgent.exe
Administrator Tools: http://www.ilient.com/down/SysAidTools.exe
Agent Upgrade: http://www.ilient.com/down/SysAidAgentUpdate.exe
MSI package for group policy: http://www.ilient.com/down/SysAidAgent.msi
We would love to receive any feedback you have on the new version of the agent.
|
|
|
Dear Evan,
When preparing a ghost (or similar) image to be used for OS replication, please install the SysAid Agent on the PC from which the image will be taken. Then perform the following steps:
1. Open the registry editor (Run -> regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Ilient\Agent).
2. Delete the "MachineID" value.
2. Change the "FirstTime" value to “Y”.
3. Create the (ghost) image.
Now, when the image is copied onto another PC, the Machine ID of each PC will be calculated for the first time upon restarting, and the correct Asset ID will be assigned to each asset.
Best Regards
Eli
|
|
|
Hey pmatsinopoulos,
Thanks for keeping us informed the issues was resolved.
Best Regards
|
|
|
Hey gilly2006,
The Post Lev provide you is the correct information on how to modify the session timeout interval
Best Regards,
Eli
|
|
|
