ఈ వారం, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, నేను ప్రజలు MSDN చర్చా వేదికల్లోకి మరియు ఇతర నివేదికను సమస్యలు రకాల ఎక్కువ ప్రశంసలు కలిగి.
చివరి వ్యవసాయ ఆకృతీకరణ:
- ఫైర్వాల్ లోపల SQL / ఇండెక్స్ / ఇంట్రానెట్ WFE.
- DMZ లో WFE.
- DMZ మరియు అంతర్గత సర్వర్ మధ్య ఫైర్వాల్ యొక్క రకమైన.
మేము ప్రాజెక్ట్ను ప్రారంభించింది ముందు, we let the client know which ports needed to be open. During the give and take, ముందుకు వెనుకకు కంటే, మేము స్పష్టంగా రెండు ముఖ్యమైన విషయాలు చెప్పారు ఎప్పుడూ:
- SSL మీరు ఒక సర్టిఫికెట్ అవసరం అంటే.
- The DMZ server must be part of a domain.
రోజు ఒక, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.
ఈ సమయంలో, మేము SSL సర్టిఫికేట్ మరియు పైగా గందరగోళం కనుగొన్నారు, పాపం, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. సగటు సమయం లో, we solution architects moved ahead with the business stuff.
A weekend goes by and the client obtains the certificate.
Our infrastructure guy shows up and discovers that the DMZ server is not joined to any domain (either a perimeter domain with limited trust or the intranet domain). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….
Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, అన్ని తరువాత, not a production solution).
Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" హోదా.
లాంగ్ కథ చిన్న, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran the configuration wizard and voila! We were in business.
</చివర>
I can almost beat your SSL certificate issue. We had everything created and were ready to extend the web app with SSL (then redirect port 80 in IIS). The administrator had a .cer file ready to go. But NONE of the options or crazy contortions to apply it in IIS will work–the site always displays a blank page like the site collection doesn’t exist.
After much banging of heads, we learned this was caused by the cert request not coming from that server. The administrator simply asked for a cert and was emailed the resulting key. With no private key, the SSL tunnel could not get built between the WFE and the browser. We wasted 1/2 day on that.