The next release of forefront client security, code name "stirling" has now a new name: Forefront Endpoint Protection 2010. The security management pieces are named: Forefront Protection Manager. This is an exciting suite of integrated entreprise security solution that spans endpoints, servers, and edge.
Here is a quote from the official team blog:
"Forefront codename “Stirling” - the next generation of the Forefront Security Suite for integrated, comprehensive protection across endpoints, servers and the edge – will be officially known as Forefront Protection Suite (FPS).
...
At WPC we are also announcing the following new product solution names:
· Forefront Endpoint Protection 2010 - current version is Forefront Client Security
· Forefront Protection 2010 for Exchange Server - current version is Forefront Security for Exchange Server
· Forefront Protection 2010 for SharePoint - current version is Forefront Security for SharePoint
· Forefront Online Protection for Exchange - currently called Forefront Online Security for Exchange
· Forefront Threat Management Gateway Web Security Service - the next generation of ISA Server 2006. "
If you would like to setup sharepoint to use a different site than the default one (port 80) for Team Foundation Server, you can do that as follows:
1- copy msiproperty.ini from the AT or ATDT folder on the installation media (depending which one you are installing) to a local folder,
2- change the property: VSTF_WSSSQL_PORT from 80 to your desired port. And then
3- start setup.exe under the subfolder of the sku you are installing with the command line: /INIFILE=<path to your custom ini file>. for instance, if you are installing ATDT and your inifile is in c:\msiproperty.ini and your CD media is on D:\, then you do the following:
d:\atdt\setup.exe /INIFILE=msiproperty.ini
Thanks,
Elyasse
Dan Kershaw, a Program Manager on Team Foundation Server team, posted this note on msdn forum:
"To ensure Team Foundation Server is ready to ship, we are asking you to respond to another survey. However, this time there is an added incentive. For the first 300 respondents who install Team Foundation Server RC, complete the survey, and submit certain log files, we are offering a special token of our appreciation. For complete details, visit this site.
Update – If the setup was successful, the log files (VSMsi*) are not in the %temp% directory. They are moved to the installation directory. Also, you should probably review the log files before sending them in the event you need to expunge any information that would upset your local IT department, such as server names or IP addresses. Just replace them with X's." <End of Dan's note>
It is very important for us to hear from you so that we can assist you in having a great TFS installation and administration experience.
During TFS install, if you recieve error 28100 (Failed to load EventService proxy object: Requested registry access is not allowed.), most probably this is due to regkey left over from a previous TFS installation. TFS uses this regkey to locate registerd servers and make calls against them.
Here is the workaround to solve this problem:
1- open regedit and go to: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers
2- locate a key under servers with the name: <%YourServerName%>
3- delete this key (not only the value, yet the entire key).
4-rerun setup.
I hope this helps.
TFS Setup have done major improvemets in the way it configures WSS. Also, we now implemented a CA that does a health check on WSS preconditions and report any issues that do not meet the TFS recommendations in clear error messages.
Sharepoint was TFS number one problem area (featured eaither during setup or in Project Creation) and I am glad to see that a great number of our customers are benefinting form a much better install experience due to these improvements.
Talking to customers and reading the blogs and forums, I saw great excitements about the major steps setup has taken to minimize the installed problems that might be caused by some WSS configurations that do not meet TFS standards.
I hope you also benefited from the WSS improvement effort, and I'm eager to hear from you your feedback on RC's install experience related to previous releases.
Thanks,
Elyasse
If you move their IIS root directory from inetpub to a different folder without copying the AdminScripts subfolder from inetpub to the new directory, WSS setup fails silently. The WSS admin site is not setup yet you won't notice it until you try to get to it.
If you try to install TFS after this you will recieve an error during TFS install: "Error 32000.The Commandline '"D:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130242250."
This is due to the fact that WSS is not installed properly and the admin site is not accessible.
If you recieve this error, here are the workaround steps:
1-Uninstall WSS
2-Copy over AdminScripts from InetPub folder to the new VRoot folder
3- reinstall WSS
4- rerun TFS setup.
I was going to write about this actually.. yet I found that askburton has already a great item for it.. so if you get this error.. here is a help link ...
http://blogs.msdn.com/askburton/archive/2005/01/27/362083.aspx
let me know if this was helpful...
Repair and Reinstall (ie. uninstall and then reinstall again) are not supported on the comming Beta2 of Visual Studio Team Foundation. If you want to reinstall or repair your application and keep your existing data, you will need to backup the data first, and then reimage the machines and install from fresh again, then restore your data on the databases.
The work to fix the repair / reinstall scenarios is going to be after beta 2. I am talking only about Visual Studio Team Foundation Application Tier and Data Tier installs. (both on different machines or on a single machine).
I would love to hear from you on how was your experience installing Visual Studio Team Foundation (both Applcation Tier and Data Tier). It is our goal to provide you with the best setup experience. Any exprience you would like to share? Anything you would like to let the VSTF Setup team to know. Any wish list you have? throw them all onto me :)
If you write a file that is intended to compile in all systems (ue, sample code file), people who compile it in a code page different than the code page that is was saved under may encounter a compiler error: "C4819: The file contains a character that cannot be represented in the current code page (System_code_page). Save the file in Unicode format to prevent data loss".
To write a C code file that compiles on all systems, you have 2 options:
1- save it in unicode (will not compile using older compilers though)
2- or if you want to support all compilers including older ones, change the following:
const static char mb_japanese[] = "....";
to
const static char mb_japanese[] = { 0x41, 0xF0, 0x72, 0xFD, 0};
this method should be done for all string types, including wchars.
Be careful when using the & operator on a CComBSTR variable. If this variable is not empty, using the & operator on it to point it to a new BSTR will lead to a memory leak.
For instance,
if you have a variable bsz1
declared and initialized as:
CComBSTR bsz1("HiWorld");
the member BSTR is allocated by issuing a call to SysAllocString. If you use somewhere after that in your code (&bsz1), you will cause a memory leak.
You can call bsz1.empty() before you use &bsz1 to prevent from the memory leak.
Cheers.
Elyasse
