Search results for query: *

What kind of calendar issues? Running TZMove.exe on the clients worked great for us.

legend3897, BES requires the CDO.dll from your Exchange Server to be copied over, so yes, it is.

I have been playing with TZMove.exe and I am having some issues. It's running on a patched workstation and says that there are no appointments to move for any mailbox I try.

scorch70, who is going to be the brave soul to test it? ;-)

RE: Dyadmin Has microsoft come to their senses?! You decide and let me know, this is for Exchange 2003, 2000, and 5.5! Did you notice that the last update to the revision history was to remove 5.5? :(

Web-based E-mail is not enabled, for security purposes. Previously this was a Windows 2000 Server with TS and clients running Outlook over the VPN had no troubles. The whole problem started when we upgraded to Windows 2003. Any other program will run flawlessly when working remotely, it is...

We use Checkpoint for VPN. The server is on a 1GB ethernet with a T1 for Internet. The T1 is shared among the rest of the company, as well.

Using VPN to connect to the TS from which users run basically everything. Internet conenction doesn't matter. Anywhere from dial-up to EDGE to cable.

We are using Outlook 2k. Locally the machine runs flawlessy, which is why this puzzles me. If I connect through RDC over the LAN, it works flawlessly, as well. It is only when I try to run it from machines connected through the VPN.

I have a strange issue. We run a Win2k3 server as our Terminal Server. This machine has approximately 20 people configured for it with anywhere from 3-5 people on it at any given time. If any user runs Outlook from the TS, the first time they try to do anything for the first time, it will...

Festus, You solution does not work. if you look at the original post, you will see that this is the last thing I tried before posting this to Tek-Tips.

hmmm... I have roaming boundaries set as 10.40.0.0. Did you do anything else recently?

Sorry I have not gotten back sooner. There is no solution as of yet, unfortunately. The Windows NT version of netsh is winscl.exe, and I have tried adding entries in via this way, but without any success. We may have to deal with legacy clients until we ungrade our NT DCs to Win2k and Active...

I tried adding the server into the LMHOSTS file with no luck. The setting for SMSSITECODE is already set to my site code. They still do not get picked up by the server.

Alright, I ran ccmsetup.exe /mp:RHPROD07 (the name of the server) and I got the same results. It HAS to be something with WINS, but I do not know what.

Interesting, there were no issues in the ccmexec.log but I did find a problem in ClientLocation.log. Here is a portion of it: ----------- Failed to resolve IP address from WINS No NLB default management point is present, attempting to resolve default management point from WINS Retrieved...

Just an update: If I install the legacy client on a machine and then remotely send out the advanced client it looks like the install works. Strange.

No, if i run an manual install from the client machine, it will not work because it cannot find the site. If i push out the install manually and then run over to the machine and type in the site code it works fine. Legacy installs work fine so I am almost positive it has to do with something...

The same server is MP, SLP, DP, CAP, and RP, since this is a test environment. Are you referring to the Client Installer account? If so, yes it has the proper rights.

Important stuff: SMS 2003 Windows NT domain Windows 2000 workstations Now my question: I am having a hard time figuring out what is wrong with my SMS 2003 setup that clients will not automatically discover my site. If i push a client out, it installs, but it never assigns to the site as a...