none
connect windows 7 to SBS 2008

    Question

  • My server is running with SBS 2008, I have 3 computers with windows XP Professional connected to it, the new computer with windows 7 Ultimate does not recognize http://connect, and it tell me that an error occurs when I try to execute LAUNCHER from the USB memory. Can someone please help?????

    Wednesday, January 6, 2010 12:57 AM

Answers

  • Ok Guys,
    bottom line, I paid an IT pro, he came in fixed it and done.
    I still don't know what he did.................
    • Marked as answer by lucote Thursday, January 14, 2010 1:57 AM
    Thursday, January 14, 2010 1:57 AM

All replies

  • Can you tell us more details? What is the LAUNCHER for? What is the detail error message when you execute the LAUNCHER?
    Arthur Xie - MSFT
    Thursday, January 7, 2010 9:29 AM
    Moderator
  • I also have this problem.  Just completed a SBS 2008 build & installation yesterday.  Started adding computers to it today & found that after using the Connect Computers Launcher, get the following message......

    Operating System Requirements

    This computer does not meet the maximum operating system requirements for running client setup.

    As I have upgraded my lan to Win 7 Professional (32bit) with one Win 7 Ultimate (64 bit), find this unsettling as Win 7 is supposed to integrate seamlessly with Server 2008.

    However, the remaining Vista Business (32 bit) connect to SBS without any problems.
    Thursday, January 7, 2010 1:12 PM
  • Issue resolved.  Out of curiosity, clicked on the link above & when the connect computer page came up, clicked on Start connector.  When the dialogue box came up, clicked on run.  Successfully added this computer I'm currently using (Win 7 Professional - 32bit).

    For successful connections for Win 7, use the Web Browser method.
    • Proposed as answer by Sirius B Thursday, January 7, 2010 1:34 PM
    Thursday, January 7, 2010 1:33 PM
  • The LAUNCHER is the ( connect computer program) this is copied to a portable media (such as a USB drive) and then you run it on the computers that you want to add to the network.
    When I use http://connect I get ((Internet Explorer cannot display the webpage)) and I do have internet connection. 
    When I try to run the connect computer program thru LAUNCHER I get
     "" An error occurred while downloading Connect Computer application. Please run this application again""
    I allready have two computers with Windows XP Pro connected to the server, I don't know what could be causing this.
    Friday, January 8, 2010 4:07 AM
  • I also had that problem when I added the 2nd machine (other 4 installed ok).  no matter what I tried, I could not connect.  So as a last resort, I restored that machine to the day before (Have WHS).

    Tried again & it successfully connected.  I assume that the connector program installs & when it fails, leaves remmants on machine preventing further attempts.  I find that by using portable media to connect, it always fails (at least on my machines).  Used web browser method on all & it succeeds.
    Friday, January 8, 2010 9:21 AM
  • I have think of that but we are talking about and out of the box, brand new laptop.
    I upgrade it to windows 7 Ultimate, and nothing more. Could it be the upgrade version?

    Saturday, January 9, 2010 12:51 AM
  • Have you tried shutting off the Windows Firewall at the service level before connecting?

    Have you tried adding  http://connect to the Internet Explorer trusted sites? (You may have to uncheck Require Server Verification for this)

    Additionally, check this link http://support.microsoft.com/kb/957708


    Another thought, since it is an upgrade you might want to install the latest version of .NET Framework. Problems with .NET Framework can cause issues with the http://connect or usb method.
    Saturday, January 9, 2010 4:48 AM
  • Ok Guys,
    bottom line, I paid an IT pro, he came in fixed it and done.
    I still don't know what he did.................
    • Marked as answer by lucote Thursday, January 14, 2010 1:57 AM
    Thursday, January 14, 2010 1:57 AM
  • I've come across this a couple of times. I've always ended up editing the supportedos.xml file in "c:\program files\windows small business server\bin\webapp\clientdeployment\packagefiles"     and adding in

      <OS id="5" Name="Windows 7, x86" Major="6" Minor="1" Build="7600" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0" />

      <OS id="6" Name="Windows 7, AMD64" Major="6" Minor="1" Build="7600" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9" />

      </SupportedOS>

      </SupportedConfigurations>

     

    I'm sure there must be a fix now, I've seen articles referring to various rollup patch fixes...but they never seem to fix the problem for me.

     

    This article makes reference to it http://www.ditii.com/2009/02/09/troubleshooting-windows-7-beta-domain-issues-with-sbs-2008/ , albeit Win7 Beta

     

    HTH

    Friday, June 11, 2010 3:31 PM
  • Thank you Lee, I hadn't seen this article before, and I'd tried just about everything else.

    Gives me something to do after church tomorrow!

    Saturday, June 19, 2010 8:53 PM
  • I've come across this a couple of times. I've always ended up editing the supportedos.xml file in "c:\program files\windows small business server\bin\webapp\clientdeployment\packagefiles"     and adding in

      <OS id="5" Name="Windows 7, x86" Major="6" Minor="1" Build="7600" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0" />

      <OS id="6" Name="Windows 7, AMD64" Major="6" Minor="1" Build="7600" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9" />

      </SupportedOS>

      </SupportedConfigurations>

     

    I'm sure there must be a fix now, I've seen articles referring to various rollup patch fixes...but they never seem to fix the problem for me.

     

    This article makes reference to it http://www.ditii.com/2009/02/09/troubleshooting-windows-7-beta-domain-issues-with-sbs-2008/ , albeit Win7 Beta

     

    HTH

    That worked for me - Thanks for the Input

     

    Andy

    Saturday, November 6, 2010 7:36 PM
  • You need this update installed on your SBS 2008 server to connect your windows 7 clients to the domain using the Http://connect.  Here's the link: http://support.microsoft.com/kb/969121
    Tuesday, April 26, 2011 6:03 PM
  • SBS "Win 7" “Connect Computer Program – Error” “An error occurred during” http://connect launcher.exe

    Here's what I did. Rollup 3 fixes all the OS version and requirement issues. The lack of ability to hit http://connect, or any other sites included in SBS can be demonstrated in nslookup. On the server run nslookup connect and the answer returns. On the client try nslookup alone, then at the nslookup carat "set d2", "set recurse", "set timeout=120", then type connect. If one or more of the numerous responses that returns says "server failed" the communication is lost to the server. The solution that worked for me:

    1. go to services in and set all the relevant services to automatic, start. There is 30 or more servises off, start all of them; This should add additional functionality to firewall and and reformat some of the queries: REBOOT

    2. Add incomming ports on your router for all the failed ports tested by SBS when you added the domain name (25, 80, 443, 987) it was in the virtual servers on my belkin.

    3. If these have not fixed it then manually add the client to the domain and try it. I did all these and when I went to check it was fixed. I can hit all the web sites included in SBS, nslookup returns flawlessly and launcher.exe works. NOTE if you added the client manually and then run launcher it may have log in problems.

    Saturday, June 4, 2011 5:31 PM