Edit Host Files
Some times in moss when you edit the host files in moss
to make a good url and then hit the url it keeps promoting for user login
i found a solution for this problem
Posts Tagged ‘Moss’
Abdel-Rahman Awad
Jun 16
|12:35
Abdel-Rahman Awad
Jun 16
|12:34
Abdel-Rahman Awad
Mar 26
|10:22
SharePoint Search By Default Exclude the Front Pages From The Search
to be able to include them you need to add the following rules
Abdel-Rahman Awad
Mar 20
|11:00
We had a problem with draging and dropping webparts between zones inside sharepoint and this is where we found our soluiton
Abdel-Rahman Awad
Feb 26
|16:18
- Create a Deployment Project under you solution structure called deployment
- Place all the xml ,xslt ,css and aspx in the right structure under the 12 folder in the deployment project
- Create Projects for code behinds , business or data layers to generate only dlls
- Add this post build events to copy the generated dlls to the GAC folder under your deployment project
cd $(ProjectDir)
Copy "$(TargetPath)" "..\Deployment\GAC"
- Add this post build events to the deployment project to generate the WSP Package and place it under the Deployment project directory
cd $(ProjectDir)
"C:\Program Files\WSPTools\WSPBuilderExtensions\WSPBuilder.exe" -WSPName $(ProjectName).wsp
This parameter “-WSPName $(ProjectName).wsp” generate a WSP Package with the name of the Deployment Project by default it the name of the project directory.
For more parameters help please run the command
"C:\Program Files\WSPTools\WSPBuilderExtensions\WSPBuilder.exe" –Help
- From the solution properties Set the Deployment project to depend on all other projects
so by this you make sure that whenever you are building the package it will contain the latest dlls because other projects will be building by default and copying the dlls to the GAC Folder
- when first time building the project it will automatically create a text file called “solutionid.txt” under the deployment project directory , that file will contain the id of the generated wsp package, it is very recommended to include that txt file into your project and check it in into TFS , so you make sure that all the team members will have the same WSP package id .
Disadvantages
- WSP Builder Includes any file included in the “File” structure of the deployment project and not the “project” structure, so any files that is hidden or not included in the deployment project structure, however placed in the physical structure of the files will still be included ,
So before each build you have to clean up your file structure from any unwanted hidden files.
- The commands lines copying the dlls to the GAC folder will also copy the external referenced dlls that is having the property “Copy Local” to true , and that will end you up deploying dlls that you don’t want to deploy or even deploying dlls that is already included by other packages which is totally not recommended.
So please make sure that any dll reference has the property “Copy local” is set to false.
- sometimes to use the WSPBuilder it is needed to create empty Folders Like "GAC" and empty folders are not physically created in the TFS , and that causes some problems when Using MSBuild tasks to Do a release on the Build Server
Abdel-Rahman Awad
Feb 7
|09:00
Configuring Web application to have Two zones windows and forms Authentication
Create the extranet site.
..Application Management -> Create or Extend Web Application > Extend
i. Set the Description
ii. Set the Port [80]
iii. Set the Host Header to [ISSExtra]
iv. Pick NTLM as the Authentication Provider (we’ll change this later)
v. Specify Anonymous Access to No (and this!)
vi. Set the Load Balanced URL Zone to [ISSExtra]
vii. Set the zone to extranet
b. Go back to Application Management and choose Authentication providers
c. Click on the Windows authentication provider link and
ii. Change the authentication to Forms
iii. Add the following as the membership provider: ISSMembershipProvider
iv. Add the following as the role provider: ISSRoleProvider
v. Save
vi. Note: Disabling client integration will remove features which launch client applications. Some authentication mechanisms (such as Forms) don’t work well with client applications. In this configuration, users will have to work on documents locally and upload their changes.
Add the host headers to DNS / hosts file!
a. For DNS (if you have access) add resolvers for ISSExtra. It should resolve to the IP address of your MOSS 2007 server.
b. If you don’t have access to the DNS server edit your hosts file to resolve the addresses.
i. Open the hosts file in notepad, this exists in the [C:\Windows\System32\drivers\etc] directory, assuming Windows is your OS directory.
ii. Make the changes to reflect the following
[MOSS Server IP Address] ISSExtra
Changes in the web config
For forms Authentication using database
i. Create sql database
ii. Run the following programme and choose the targeted database and run through the wizard. <WindowsDirectory>\Microsoft.NET\Framework\<version>\aspnet_regsql.exe
iii. In the web.config of the central administration
Add the following tags with your configuration
After </SharePoint> tag.
<connectionStrings>
<add name="MembershipDatabaseISS" connectionString="SERVER=localhost;DATABASE=ISSBasic; TRUSTED_CONNECTION=true;"/>
</connectionStrings>
Inside <system.web> tag
<membership>
<providers>
<add name="ISSMembershipProvider "
type="System.Web.Security.SqlMembershipProvider,System.Web, Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="MembershipDatabaseISS" enablePasswordRetrieval="false"
enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
requiresUniqueEmail="false" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10"
passwordStrengthRegularExpression=""/>
</providers>
</membership>
<roleManager>
<providers>
<add name="ISSRoleProvider " connectionStringName="MembershipDatabaseISS"
applicationName="/" type="System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
</roleManager>
iv. On both the intranet and the extra net application web config add the following
After </SharePoint> tag.
<connectionStrings>
<add name="MembershipDatabaseISS" connectionString="SERVER=localhost;DATABASE=ISSBasic; TRUSTED_CONNECTION=true;" />
</connectionStrings>
Inside <system.web> tag
<membership defaultProvider="ISSMembershipProvider">
<providers>
<add name="ISSMembershipProvider"
type="System.Web.Security.SqlMembershipProvider,System.Web, Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="MembershipDatabaseISS" enablePasswordRetrieval="false"
enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
requiresUniqueEmail="false" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10"
passwordStrengthRegularExpression="" />
</providers>
</membership>
<roleManager enabled="true" defaultProvider="ISSRoleProvider">
<providers>
<add name="ISSRoleProvider" connectionStringName="MembershipDatabaseISS"
applicationName="/" type="System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
/>
</providers>
</roleManager>
For forms Authentication using AD
Same as forms Authentication using database section but with modifying
The connection string to
<add name="MembershipDatabaseISS" connectionString="LDAP://testdomain1.test.com/CN=Users,DC=testdomain1,DC=test,DC=com" />
2. Add the attribute for both the <add name="ISSMembershipProvider "…
And <add name="ISSRoleProvider "…
connectionUsername="testdomain2\administrator"
connectionPassword="password"
Abdel-Rahman Awad
Jan 23
|11:49
Abdel-Rahman Awad
Jan 23
|11:28
Very clever link that Describe all about Modifying The menus in MOSS From code behind Quick Launch
Abdel-Rahman Awad
Oct 25
|07:58
Are you trying to install a new MOSS 2007 virtual image
and don´t know what is the right configurations to set.
Well my helpful friend Carsten have gave me a very useful link
I wanted to share with you it describe in detailed steps how to
make a new MOSS 2007 Virtual Image and it also provide you
with the right configurations to set.
The installation Steps is located at : (here)
