I'm trying to install SCCM 2007 on my Windows Server 2003 SP2 servers. One isrunning SQL 2005 SP2 and the other will be a site server hosting all the SCCM components. While running the pre-req check from my site-server-to-be the 8.3 short file name check fails on the remote SQL server. Yes, I located the MS KB article on how to enable the 8.3 naming generation using the command line. Irebooted the server after the change. I also checked the registry key, and it's set to "0". To my knowledge, this feature was never disabled on the servers. The error excerpt for the SQL server is: <06-04-2008 14:50:41> Rule Name: Short File Name (8.3) Support (Site system)<06-04-2008 14:50:41> Result: Error<06-04-2008 14:50:41> Setup either could not verify that short file name (8.3) support is enabled on the computer specified for site system installation or the server could not be contacted to determine short file name support information. No further prerequisite checking rules can be evaluated on the specified system. Setup cannot continue. The rest of the checks that were performed passed, so it can contact the SQL server. I ran the pre-req checker on the physical SQL server and _no_ 8.3 name generation warnings were shown. In fact, I get this in the log for both servers it checked: <06-04-2008 15:03:51> Rule Name: Short File Name (8.3) Support (Site system)<06-04-2008 15:03:51> Result: Passed Is there a way to force the bypassing of this check? From all indications this is a false positive and the installer will not let me proceed. This is pretty urgent. Thanks!

I'm seeing some more odd behavior. If I run the checker locally on the SQL server and input "localhost" for both the SQL and site server name, I get two failed 8.3 name checks plus and 'unsupported operating system' error. However, as stated above, if I input the actual hostname of the SQL server then I don't get a failed 8.3 check or unsupported OS message. Also, for the failed checks when inputting 'localhost' it resolves the name to the actual host name for the first two checks that come up warnings...schema and WSUS SDK. Then it shows "LOCALHOST" for the error messages.

Is the 8.3 the only error are you getting? nothing about admin$ share? Is it a SQL Cluster?

Did you ever get around this? I'm having the exact problem.

Yes, that's the only error and the SQL server is not a cluster.

JaredCM1 wrote: Did you ever get around this? I'm having the exact problem. I did not. I ended up installing a local SQL instance on the SCCM server to get around the problem.

I know if the prereq checker can't access the Registry of a system remotely, it will report that error (at least I've seen it do so before). So I'd validate that Remote Registry access is available.

Hi Wally, Thanks. I had the exact same problem, and as you presumed it was the "Remote Registry" service on the SQL server that had not been started, I started it and every thing installed just fine.

Did you ever get around this? I'm having the exact problem. I had this issue and I found out that the user account I had logged in on the CCM server was not a local admin on the remote SQL server. Once I did this, my Pre-req checked out correctly. Try this and let me know if it helped. I know this is an old post, but you never know if someone is looking for the answer still. JW

Run the following commandfsutil.exe behavior set disable8dot3 0This solved my problem.

Thanks, this solved my problem when I got this error.RobinRobin Wilson

I've also found on SCCM 2007 SP2 connecting to a Windows 2008 R2 server that will hold the SQL database, that the account I'm using (domain user account) to run the pre-req checker needs to be a local administrator on the Windows 2008 R2 server that will hold the SQL database as well as the server where SCCM will be installed (not just the machine account as documented at http://technet.microsoft.com/en-au/library/bb693554.aspx). Otherwise I get the 'Setup either could not verify that short file name (8.3) support is enabled on the computer'

Hi, on Windows 2008 R2 I want to install SCCM and getting the "Short File Name (8.3) Support (Site system)" error, too. I using a seperate SQL 2008 Server running on another Windows 2008 R2 Server. Here's how I fixed to problem: first I run "fsutil 8dot3name set 0" on the server where I tried to install SCCM -> result: it still did not work! (same error like above) than I run "fsutil 8dot3name set 0" on the SQL Server and ... -> result: it worked ! :-) So you have to get 8.3 working on the SQL Server not on the sccm ... Hope that helps... :)

Thanks! this works like a gem.

In addition to enabling Short File Name support on the SQL Server, I had to add the service acct I was using on my SCCM server to the local admin group on the SQL Server. That allows the SCCM installer to access the Remote Registry Service on the SQL server to verify the reg entry responsible for the Short File Name support.