| Author |
Message |
|
|
At first we used to rollout with the depolyment tool which worked fine. Now we just rollout from the Network Discovery / Deploy agents section. Then via our login utility (Scriptlogic Desktop Authority) I push out the required registry settings for the terminal servers.
Alex
|
|
|
Hi Kdouce,
I have not had any issues with 2008R2 and multiple terminal servers. In my network, all servers are 2008 or 2008R2, and all terminal servers are 2008R2. The only change you need to make on the registry of the terminal servers is the change listed in the following post so that the agent knows it is a terminal server.
http://www.ilient.com/Sysforums/posts/list/531.page#2315
Alex
|
|
|
Hi Andy,
You need to restart the Sysaid Server Service, not IIS.
Alex
|
|
|
I have Sysaid agent running on 3 2008R2 Enterprise Hyper-V servers without any issues. Didn't have to do anything special that I am aware of to get the agents to install or to get the services to start. The only real setting we have on our system that may have something to do with it is UAC is globally turned off via GPO. Possibly try turning off UAC and see if you can get them to run then?
Alex
|
|
|
Hi GMurison,
We have been running SSO since 2008, and then again after we upgraded to 2008R2 we have not had any issues with it. We did have some "funky" issues with it when we first got setup but those were fixed with an update when we opened an SR. I would recommend that you go the route of opening an SR with support. They should be able to square you away fairly quickly on this issue.
The only thing I have different in my serverConf.xml is the following:
<ntlmParam>
<ntlmParamName>jcifs.smb.lmCompatibility</ntlmParamName>
<ntlmParamValue>2</ntlmParamValue>
You have yours set to 3 whereas mine is 2. Not really sure what the difference there is between 2 and 3 but it may be something that you can try before opening a SR. If it doesn't work then, I would recommend that you go the route of opening an SR with support. They should be able to square you away fairly quickly on this issue.
Alex
|
|
|
Hi Tommy,
We currently monitor around 225 systems with Sysaid. Have not really noticed any of the perfomance issues that you have mentioned. Currently our Sysaid server runs on a Hyper-V Virtual Windows 7 x64 with 4GB ram, and 4 virtual cores the database backend is on a remote Microsoft SQL server. I haven't noticed any real perfomance drain with having all these systems monitored. We also monitor / inventory all our SNMP capable devices which brings the number up to around 335 devices monitored one way or another.
Alex
|
|
|
Was also the same procedure for me as well, suggest contacting support if you have this issue as the fix may not apply to all.
Alex
|
|
|
Hi VedranS,
I was getting ready to send in ticket on this very issue. It appears (from what I can see in the logs) that the update routine for the importing of the inventory agent files, only runs once at startup witht the Sysaid Server service, and then it shutsdown after 2 minutes. It only started happening since the install off the 7.5.06 so if the same version for you, I think they are related. The way I have gotten around the issue so far is to schedule the server service to start and stop nightly at 5 minute intervals 3 - 4 times and then they agent files process out of the directory.
I will update again, once I have generated the ticket and have gotten a resolution.
Alex
|
|
|
|
In the upper right hand corner when you open SysAid, it will tell you the version number and edition as shown in attached image example. In my case, I applied the Pro verion upgrade.
|
|
|
Normally I would create a new category with the name that you want to change to. Then select the old category and select delete, you should then be prompted to reassign all those tickets that are under the current category to the new category.
Hopefully that helps,
Alex
|
|
|
Hi Itay,
I just installed on test machine w/ logs on, will update the SR if / when I see the performance hit.
Alex
|
|
|
Hi Techguy,
I will see if I can find my note from when I set this up. Basically I used the same "impersonate" commands that Blackberry Enterprise Server uses when setting up an account for it w/ Exchange.
Those commands were:
Now in the case above change "BES Admin EWS" to "SysAid" and the "BESAdmin" to the user account you are using with Sysaid for Exchange integration.
Then the next step after that is to run the command from the Exchange Command Console on the CAS server:
Note: Please replace "servername" with the actual name of your Client Access Server.
You don't need the CDO objects installed as Sysaid's implementation has that built in.
Hopefully that works for you. It took some trial and error on my part to get it to work.
Alex
|
|
|
I am working on getting another computer setup for testing so that I can collect some logs, I will probably have it operational sometime next week as I have been out of the office most of this week.
Alex
|
|
|
Have deployed to various computers and have found the following:
- On Windows XP machines: IliAS.EXE consumes 100% of the CPU
- On Windows 7 machines: the computer basically stalls out, even though the CPU is running at about 20 - 30%.
Removing agents and then redeploying 7.0.05 resolves these issues.
|
|
|
Hi Itay,
I have installed it on my BB Bold 9650 no issues with it so far. The only thing that I would like to see on both the iPhone and the BB app, would be the option to email from within the app.
Thanks,
Alex
|
|
|
