1 of 1 people found this helpful
Check your permissions on your ldmain\ldscan directory, 'LANDesk Script Writers' group probably doesn't have write access to this folder.
Thanks for thinking with us.
I've changed the rights on the ldmain\ldscan folder, and child objects to Write(before there were indeed no Write rights).
Restarted the console with a test user, but the problem unfortunately still exists.
Any other suggestions?
* In addition: We've also tried to add the testuser to the local group Landesk Provisioning, but this also didn't have the desired effect....
Message was edited by: kevlar
I hate to ask but are your Tech's in the LANDesk Management Suite and LANDesk Script Writers groups?
I had a hard time getting this working also (needed to give write access as mentioned above), but your other settings seem to match mine.
So it should be working otherwise.
The test user which I am using is member of a global security group in our Active Directory. Every tech in our company which needs to use LANDesk is member of that group. That group is member of the local LANDesk Management Suite group on the core server.
The LANDesk Scrip Writers group on the server had no members, but I've added the test user and gave the group write rights on ldmain\ldscan folder.
But it still doesn't work.
It is possible to view the bare metal server devices
I can add devices without any error messages(so it seems)
But it never shows up in the bare metal server devices.....
Anybody any other ideas?
It seems to be solved now with the test user.
The problem was, that the Script Writers group had Write rights on the \\Coreserver\ldmain\ldscan folder, but they needed also the Modify right....
What a difference one checkmark can make..