7 Discussions started
10 Comments posted
5 Points earned
1 Solutions given
- Last Active
- FSAccount, MyAccount
800+- Clients and 80 servers are managed bij the PMS. Server is running within VMware. HW version 9 (current with the esx version running @ this moment) Latest VMware tools installed. 1 CPU 2GB mem (enough for when it is operating normaly) When it is running smooth then it uses 1.2/1.3GB and load on cpu between 5 and 20%.
We didnt fix it yet. The problem didnt pop up for 2 weeks now i think. And today i have had one machine that had the problem, Only the machines was removed before i was able to do a FSDIAG
Checked the logging All is succesfully. It doenst display to what server it is connecting. I have opened a support ticket Included 3 FSdiag, one of a server that is still connecting towards the old server. one of the old server and one of the new server. Just received the message that it is being investigated
If you mean this 3. On the new server untick and retick some management agent setting from policy domain root level (for example the final setting on F-Secure Management Agent -> Settings -> Communications -> Protocols -> HTTP -> Management Server Address). Make sure you just untick it once and then retick it so that the…
Possible issue found. The new hostname was completely diffent from the other machine. And in the policymanager there was no autoimport rule with the new type of new. I don't understand why it displayed the file correctly. But after making a new autoimport rule it worked again.
OS : Windows 7 Pro 32 Bits NL Service Pack 1. All up to date. Both systems are the same. Only changes that have been made are to some register settings that belong to a differnt application. When i start the application i see the App-v starting, and when it tries to start Internet explorer we receive a message that…
I could not find a action.log anywhere. Checked the complete harddrive. I think that it is a permissions problem and i am trying to fix the permissions. I thought i posted the Windows logs but i forgot to do so. Logboeknaam: Application Bron: Application Virtualization Client Datum: 12-6-2012 11:52:38 Gebeurtenis-id:3079…