1 of 1 people found this helpful
You want to become familiar with Local Scheduler.
You can see your local scheduler tasks on a client with this command:
C:\program files\landesk\ldclient\localsch.exe /tasks |more
Or on 64 bit
C:\program files (x86)\landesk\ldclient\localsch.exe /tasks |more
You will see a task that runs a miniscan but has a Frequency of 600 and a filter of "IP Address Change".
By default, the agent does a miniscan on IP Address change. Then, if both the IP Address changes and 600 seconds (10 minutes) goes by, it sends another one.
So, in your scenario, I would expect since at Bootup the IP Address changes from 0.0.0.0 to VLAN A's IP, that may trigger the IP Address change a miniscan with VLAN A's IP might be sent. So a user logs in right away (inside the 10 minute frequency), the IP Address changes again to VLAN B, you should get a miniscan approximate 10 minutes after the first one with the new VLAN B's address.
Play with the local scheduler settings and test them out.
Thats great information cheers.
Just checked out my local scheduler and there is no setting for miniscan.exe. Could this be a potential problem that I have?
If I set up a schedule for miniscan at just IP address change this should cause a IP adress update at the point of entry into VLAN A and when the user logs into VLAN B is this correct?
Also if the miniscans are running every 10 min on 2000 PC wont this cause alot of network trafic?
A default agent with no changes has it in 8.8 and 9.0, so your agent must have been altered to not do this.
If you create a new agent and you don't make any changes and install that, does it have the proper local scheduler tasks?