Search results for query: *

Or you could install Gateway Services for Netware - I've used it in the past and it seems to be OK. Can't say I've noticed the Novell client slowing things down too much - probably depends what version of netware you're running?

I assume you've done the basic tests - can the XP machine ping the server, etc? I've found that XP isn't happy without a DNS server - have you got one?

Probably not without packaging it. Why do you need to use the MS version of the client?

Check the permissions on the actual CAP share - your users may not have rights to it - if they can't access the contents of the CAP, nothing will install.

Anyone out there know a good spam filter for Exchange 2000?

What licencing option have you gone for?? Per seat burns through licences more slowly than per connection.

What does your script do?

Can the client actually connect to an available CAP?

Do your users roam between machines?? If not, asign a login script with the SMS client install lines to your managed users. How are you choosing the machines not to install on?

IE6 did nasty things to my ME machine too. If you can get the tasks up, try running msconfig as a new task - then have a look at http://support.microsoft.com/default.aspx?scid=kb;en-us;Q267288 for instructions on how to perform a clean boot. Good luck!

Look at the built in group Account Operators.

I must be getting old ... heartbeat discovery is an update method and only works if you have logon discovery enabled ... so it's a red herring as it should have no effect on the status of your clients.

Hmmmmmmmmm.... I've had similar problems with security - if your SMS service accounts don't have domain admin rights, do they have local admin rights on your workstations? Are the rights nice and open on the local SMS directory and the registry keys? I've had similar problems of clients...

Back to the original question .... I wrote a Wise script to clear out the old profiles ... less painful than deleting clients.

The 60 to 90 day uninstall relates to loss of contact by the client with SMS - we have a problem with laptops users who don't come into the office very often. A client will uninstall pretty quickly if you give it an IP address outside of the boundaries. Back to the original problem - I've seen...

You run smsman manually from your current session. What did the rest of your post mean?

Similar problems - try changing the destination platform to 32 bit rather than 16/32 bit.

I've been an MCSE for a few years now and I've watched the qualification devalue over time, to become almost an entry level technical qualification. I was a VC++ programmer before going freelance on the technical side of the street and going with the flow into a series of senior infrastructure...

I'm assuming that any exe or bat that you're trying to call as a program is actually in the root of the folder that you defined in Package Properties> Data Source> Source Directory - and that you refer to it as a URL. I've found before that the client doesn't like sub-folders. It also doesn't...

Changing to run with user rights might not work if the user doesn't have that rights to the bits of the registry that you're trying to change. A better option is to run with admin rights, but select 'Use Windows NT client software installation account' - which you can set through Site...