Search results for query: *

use an exchange system manager, expand all the views, find default exchange server name right click -properties-security. Make sure that you understand what you are doing with rights (send as , recive as -especially). I hope it helps, Sam.

You have to be able to open the item, of cause within 2003 domain. Test with several MS Outlook 2003 clients0-accounts first before proceeding and then go trough AD (exchange permissions) within Exchange sys admin (be really careful). I hope it helps, Sam.

Just a heads up: go to user advance exchange properties and uncheck (hide users from address) checkbox. Cheers, Sam.

First thing; OWA 2003 is not designed to list Global addresses through web-access (basically you are tweaking the system by typing a space and search which will work). If your user's exchange advance propreties are set to hide user in the global address they will not show up under the search...

It can be sevral things involved: How did you name your second server, same as first? Did you reflect the second server in DNS records, are they pointing to second server ? Is your IIS configured properly on it and owa properties on IIS are correct? I think it is a start. Sam.

Try deleting server computer account from the domain first and clear manualy the metadata within Active directory, it still referencing everything to the old SID and RID and computer account and it must be recreated. Join the server to domain again when above is done and you will have no...

disable firewall and try to ping around and get to the internet... It is a start... Sam

here the info on setting up without using a VPN: http://office.microsoft.com/en-us/assistance/HA011402731033.aspx http://www.msexchange.org/tutorials/outlookrpchttp.html I hope it helps, Sam.

Check his calendar permissions. Set default to view or add other users as a viewers on his calendar. Sam.

The renaming machine not going to help. Fist thing--> check if SP2 was silently installed on clients. (Start-->run-->winver, check results). Check if you have SP1 on Windows 2003 server installed. Second thing-->Domain Policy/OU policy GPO, try to move machines to the neutral OU...

Read again, go to Start-->control panel-->administrative tools-->services. Find Task Scheduler service and do what I have explained,test it. Regards, Sam.

The other simple solution is insert the NIC at the same slot where the old one was placed. Most of the time it happens on Proliant Servers. I hope it helps. Sam.

to separate problem, try to move this machine account to another OU-->example: Computers on AD domain. Restart machine and run in command prompt: gpresult, check where policy are coming from. If this would not work you will need check or re-create a user profile. I hoe it helps, Sam.

Go to SERVICES and check the properties for Task Scheduler service. Go to LOGON tab and check under which logon-account the service is running?, try to switch from system account to your admin account, restart service and check again. Check RPC service in the same manner. I hope it is a...

The reason is that every time some one uses RDP/RDC the session is logged to a terminal server manager. You have to basicaly go into Terminal Services Manager find that session and reset the session to zero. No restart necessary. And check how many concurrent RDP connections at giving time are...

Hey Mark, read this also from different thread: shughesPB (IS/IT--Manageme) 30 Apr 05 0:03 I have the same problem with one user in particular that likes finding ways around OU policies. So far it’s a weekly thing to keep adding things to the disallowed list of programs he can’t run. You can...

Funny, It should work, just type NET SESSION (do not type word switch). Regards, Sam

The hashing policy (which you mentioned)is working if path for excutables is the same. The tricks which savy user do is , they can install this little IM apps in My Documents folder without having Admin Rights and run it within. Regards, Sam.

Or simply use command: NET SESSION /switch

Here is a bad news for you; You can not block completely your IM programs with only using the group policy. Sam,