July 2009 - Posts
These are the tested scale for the MOSS environment. The maximum they tested was 50 million items.
Estimate performance and capacity requirements for search environments
Here is an overview video. This is really good lead in for working with the next SharePoint Technology and WSS information.
Overview Video
This is a sample site that shows our SharePoint training offering that can be taken and user access tracked.
Home - SharePoint Training
This is pretty cool if it is true…
I have not heard for sure, but I definitely urged the management to have a “showcase” as well.
Leak: Inside the Microsoft Store With Wall-Sized Screens and the Answers Bar
Using the scope parameter, you can change the scripting levels for the current user only.
PowerShell V2 makes this reality much more transparent through a concept called “Execution Policy Scopes.” In V1, the scopes are as follows. Items on top, if defined, override items below them:
- Machine-Wide Group Policy
- Current-User Group Policy
- Machine-Wide ExecutionPolicy (stored in HKLM)
In V2, the scopes are as follows, with “Process“, ”CurrentUser”, and “LocalMachine” now surfaced as the –Scope parameter to Set-ExecutionPolicy
- Machine-Wide Group Policy
- Current-User Group Policy
- ExecutionPolicy parameter to PowerShell.exe
- PSExecutionContext environment variable
- Current-User ExecutionPolicy (stored in HKCU)
- Machine-Wide ExecutionPolicy (stored in HKLM)
Windows PowerShell Blog : PowerShell’s Security Guiding Principles
If you need to run PowerShell scripts from another application, here is a way you can do that.
Introduction
My previous article showed how to run PowerShell scripts from C#. That implementation was limited in the sense that it would run scripts synchronously, blocking until the script finished what it was doing. That is fine for short-running scripts, but if you have long-running or even never-ending scripts, you will need asynchronous execution. This article shows just how to do that.
CodeProject: Asynchronously Execute PowerShell Scripts from C#. Free source code and programming help
Now HERE WE GO!!! This is how you can make the Active Directory commandlets work for Windows 2003 directories. You have to install this web service and then the commandlets will work in PowerShell for older Domains.
Active Directory Powershell Blog : Use Active Directory Powershell to manage Windows 2003/2008 DCs
Funny…
http://www.biblegateway.com/passage/?search=Matthew+20:1-16
The funny thing about this parable is that the point of this is that all are the same in the eyes of God.. Wither you join first of last, you receive the same. In the case of the vineyard, just because they worked longer, they agreed to work for the same amount. Treating everyone the same is the point of the parable. Not the rights of the workers. If they agreed to a denari per hour that would be different.
Daniel makes a good point here… Microsoft has usually done a great job when interoperability is the goal. .NET including the Oracle provider before Oracle really supported it was a big plus for developers and those using oracle databases.
Looking at the comments, losta of developers are not happy about it either. Well we will see where this ends up, but keep it in mind if you are trying to use Oracle, migrating to ODP.NET might be your only option.
http://blogs.msdn.com/adonet/archive/2009/06/15/system-data-oracleclient-update.aspx
Daniel Morgan: Microsoft deprecates System.Data.OracleClient in .NET 4.0
More Posts
Next page »