Archive for the ‘Windows’ Category

You may have a client or user who receives the 0×85010014 error when trying to synchronize his mobile to an Exchange server. In my case it was with a Verizon Treo.

I couldn’t figure out for the life of me what the heck to do. I knew there was something wrong in IIS, because I had just previously created a new site and I didn’t think it was coincidence that the synchronization all of a sudden stopped working.

Basically, I knew it was my fault and I had to fix it…..aaaahhhhh.

So I did a little research, well you know, I googled it. That’s research!

I kept running into sites that had the same solution:

Problem:

ActiveSync will not work when the /Exchange virtual directory on the Exchange back-end servers is configured to require SSL.

Solution:
Remove the port 443 from the default web properties in IIS Manager snap in.

Well, that was not the fix in my case…..

That’s until I found this:

Note These steps affect both Outlook Mobile Access connections and Exchange ActiveSync connections. After you follow these steps, both Outlook Mobile Access and Exchange ActiveSync connections use the new virtual directory that you create.
1.     Start Internet Information Services (IIS) Manager.

2.     Locate the Exchange virtual directory. The default location is the following:
Web Sites\Default Web Site\Exchange

3.     Right-click the Exchange virtual directory, click All Tasks, and then click Save Configuration to a File.

4.     In the File name box, type a name. For example, type ExchangeVDir. Click OK.

5.     Right-click the root of this Web site. Typically, this is Default Web Site. Click New, and then click Virtual Directory (from file).

6.     In the Import Configuration dialog box, click Browse, locate the file that you created in step 4, click Open, and then click Read File.

7.     Under Select a configuration to import , click Exchange, and then click OK.

A dialog box will appear that states that the “virtual directory already exists.”
8.     In the Alias box, type a name for the new virtual directory that you want Exchange ActiveSync and Outlook Mobile Access to use. For example, type exchange-oma. Click OK. If exchange-oma already exists, you have to delete it.

9.     Right-click the new virtual directory. In this example, click exchange-oma. Click Properties.

10.     Click the Directory Security tab.

11.     Under Authentication and access control, click Edit.

12.     Make sure that only the following authentication methods are enabled, and then click OK:
•     Integrated Windows authentication
•     Basic authentication

13.     Under IP address and domain name restrictions, click Edit.

14.     Click Denied access, click Add, click Single computer, type the IP address of the server that you are configuring, and then click OK.

15.     Under Secure communications, click Edit. Make sure that Require secure channel (SSL) is not enabled, and then click OK.

16.     Click OK, and then close the IIS Manager.

17.     Click Start, click Run, type regedit, and then click OK.

18.     Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MasSync\Parameters

19.     Right-click Parameters, click to New, and then click String Value.

20.     Type ExchangeVDir, and then press ENTER. Right-click ExchangeVDir, and then click Modify.

Note ExchangeVDir is case-sensitive. If you do not type ExchangeVDir exactly as it appears in this article, ActiveSync does not find the key when it locates the exchange-oma folder.

21.     In the Value data box, type the name of the new virtual directory that you created in step 8 preceded by a forward slash (/). For example, type /exchange-oma. Click OK.

22.     Quit Registry Editor.

23.     Restart the IIS Admin service. To do this, follow these steps:
a.     Click Start, click Run, type services.msc, and then click OK.
b.     In the list of services, right-click IIS Admin service, and then click Restart.

Note If the server is Microsoft Windows Small Business Server 2003 (SBS), the name of the Exchange OMA virtual directory must be exchange-oma.

This was a real pain….

I was installing Symantec Corporate on a MS 2000 server because it did not meet the minimum requirements to install teh new Symantec Endpoint.

The console installed perfectly, but I could not get the server portion installed. I kept getting the error “Network name cannot be found” although the program was able to see the server on the network. Didn’t make sense, until I found this lil tid bit…. I love google!

“Typically this is the error we get when we cannot connect to the administrative share. From the machine with the SSC installed, try connecting to the C$ share on the remote computer before trying the install. If this doesn’t work, then the install will fail.” This is from the Symantec support forum and of course a solution was not posted but it pointed me in the right direction. I needed to restore the administrative shares on the server.

This is what I did:
1.Click Start, and then click Run

2.Open box, type regedit, and then click OK.

3.Locate and then click the AutoShareServer value in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Note: The AutoShareServer value must be set as a REG_DWORD type. When this value is set to 0 (zero), Windows does not automatically create administrative shares. This setting does not apply to the IPC$ share or to shares that you create manually.

4.Either delete the AutoShareServer value or set the value to 1.

To do so, use one of the following methods:
•To delete the AutoShareServer value, click Delete on the Edit menu. When you are prompted to confirm the deletion, click Yes
•To set the AutoShareServer value to 1, click Modify on the Edit menu. In the Value data box, type 1, and then click OK

5.Quit Registry Editor.

6.Stop and then start the Server service:
a.Click Start, and then click Run
b.In the Open box, type cmd, and then click OK
c.At the command prompt, type the following commands, pressing ENTER after each command:
net stop server
net start server
d.Type exit, and then press ENTER.

It was that simple really.

ICANN (The organization that handles the core DNS system for the internet) released a statement back in 2007 and, in short they stated that one of the 12 root servers is going to have a different IP address.

This means that most administrators had no idea that the IP address had changed.  According to this blog article ICANN let the IP address go, and some rouge server was put in its place. This means that they had 1/12th of the internet in their hands.

If you run a Windows DNS server you need to update this root hint manually.

After clicking OK you will need to reboot your server. It seems that even restarting the DNS server service will not force it to reload these settings.

Yes, you read it right. Windows Vista just came out and already it seems Microsoft is working on another disaster operating system. This excerpt is from their Vista Team blog:

” I thought I would spend a minute giving you an update on where we are. First, yes, we are working on a new version of Windows. As you likely know, it’s called Windows 7. We are always looking for new ways to deliver great experiences for our customers.”

I guess Vista is not making enough of a storm.

Over at Crunchgear, they were able to get their hands on some screenshots of this newer Windows 7 OS being put together by MS. It does seem a bit intriguing.

A doozy for sure… but no fear, Dumb Technician is here!

This was actually an easy one. The error basically is given because an attempt to write to the registry was denied due to insufficient rights. That’s Microsoft for you, nothing simple.

This is how I was able to fix and there are other solutions!

1. I was able to turn UAC off.

2. Go to start and type msconfig  and hit enter.

3. Select tools from the above tabes and select disable UAC and reboot.

Then hit Start > run cmd and at the prompt enter each line:

cd c:\windows\system32
regsvr32 xxxxxxxx.ocx