Got the info from Under the Stairs, but decided to echo it here as it is so useful to know. Not all KBs are ready though. In the end, this is the link you want to have: https://support.microsoft.com/contactus2/emailcontact.aspx?scid=sw;[LN];1414&from=KBHotfix&WS=hotfix
And may I add: It was about time...
PowerShell has a range operator. I you want to express the numbers from 1 to 5, you can specify that as 1..5. 1..5 actually build an array (object[]). One question I had during training was: Can the range operator be used on characters? The simple answer is no, but you can achieve the same with a small work around. Say you want to check the drive letters between F and M -
[char]"f"..[char]"m" | Foreach-Object { "Checking " + [char]$_ }
if the numbers are not in a sequence, you can use on of these -
"fgmr".toCharArray() | Foreach-Object { "Checking " + [char]$_ }
"fgmr".getEnumerator() | Foreach-Object { "Checking " + [char]$_ }
"f","g","m","r" | Foreach-Object { "Checking " + [char]$_ }
BTW: The range operator is limited to 50,000 elements - try 1..60000 and see the error message. If you need to go from 1 to 100,000, you can either do a for statement -
for($i=1;$i -le 100000;$i++) { blah }
or
1..50000+50001..100000 | { blah }
Got inspired by Oisin / Nivot Ink.
In line with the Windows Server 2008 posters, there is also an Exchange Server 2007 Component Architecture poster available on MS Downloads.
These are from the Office SP1 Whitepaper
Following are the KB articles referenced in the SP1 xls file
Find SP1 on Microsoft Update or at the download site.
Well, sometime I feel like nothing, null, zip, empty - but do they have to remind me???
On the other hand: A null may need some eLearning...
Small, but useful if you like I do change the font size all the time (e.g. for presentations/training/old eyes) -
param($fontSize=14)
Set-ItemProperty HKCU:\software\microsoft\notepad iPointSize ($FontSize*10)
If only Notepad supported Ctrl + Scroll Wheel for zooming...
Group Policy settings - including Software Restriction Policies - can easily be disabled - even by a standard user. Terrible! Read the full story in Security UPDATE from WindowsITPro magazine this week. The article sums up the story so far and contain links to other relevant articles.
Some of those articles require an account to read, so if you want to get to the hard facts right away, see the GPCul8r tool. I exteacted this from the readme.txt -
============
How it works
============In order to do its thing, GPCul8r.dll needs to be loaded into the process space of whatever program needs to bypass group policy. Once loaded, GPCul8r works by detouring calls to the ZwQueryValueKey function to see if the program is querying one of the keys related to a group policy setting we want to bypass. If so, GPCul8r returns STATUS_OBJECT_NOT_FOUND, thereby tricking the caller into thinking the key doesn't exist.
GPCul8r being a quick & dirty little tool is not configurable. The targeted key names are hard-coded in the source. They are:
- TransparentEnabled (controls software restriction policy settings)
- ProxySettingsPerUser (controls access to the IE proxy settings dialog)
- DisableRegistryTools (duh)
- DisableTaskMgr (duh)For more on the technique that GPCul8r uses, see Mark Russinovich's original article on the subject:
http://blogs.technet.com/markrussinovich/archive/2005/12/12/circumventing-group-policy-as-a-limited-user.aspx
The consequence: Everything below User Settings\Administrative Templates - e.q. every policy user level (as compared to kernel level or system level) code pulls out of the registry can be bypassed! If you want to counter this - read Mark's comment -
The bottom lines is that full control of an end-user environment is possible only with strict lock-down of the programs users run, something that you can accomplish by using SRP in white-list mode, for example. It's also important to note that the ability of limited users to override these settings is not due to a bug in Windows, but rather enabled by design decisions made by the Microsoft Group Policy team.
I do not know, whether Vista improves this - but I certainly hope!
So you've download Exchange 2007 SP1 and want to install it on your UM server that is integrated with OCS!?
If this is your first OCS integration then you should start is by downloading the documentation and if you've earlier downloaded the Office Communications Server and Client Documentation Rollup then you should go to the Office Communications Server 2007 Technical Library and find the documents updated to version 1.1 (Quite a few of the planning and deployment guides are updated to version 1.1 - not the Enterprise Voice Planning and deployment guide though)
Then the next place you should start reading is the SP1 Release Notes and especially the part covering Unified Messaging and "Issues related to the Unified Messaging server role"
In short the important general issues are -
And most importantly when integrating with OCS the following issue apply -
There are a few other smaller issues applying to OCS/UM but the above is by far the most important one (And I guess hours could be spent troubleshooting if you are not aware of this issue)
As announced yesterday in the TechNet flashes Exchange 2007 SP1 is now available for download here.
Of course I'm most interested in the Unified Messaging enhancements, but there many other interesting improvements as the import/export of PST files which is very interesting for our migration projects (And we also look forward to better stability of the product due to all the included fixes)
Following is an overview of the changes from the download site -
Anywhere Access
Operational Efficiency
Built-in Protection
Note: The script has been updated, see this post.
One of the best features of PowerShell is the ability to do the same on the command line as in a script. Even Command Prompt do not support than.
But as VBScript is not dead yet - I'm currently doing more than 3000-lines of it - this script is useful as it allows you to execute VbScript interactively. It has two uses: 1) Test VBScript details without having to run a huge script 2) Use VBScript features than you do not know how to do in PowerShell.
The script Invoke-VbScript.ps1
param($vbCode,[switch]$ExecuteStatement)
function PrepareVB {
$vb=new-object -com MSScriptControl.ScriptControl
$vb.language="VBScript"
$vb
}
$vb=PrepareVB
if ($ExecuteStatement.isPresent) {
$vb.ExecuteStatement($vbcode)
}
else {
$vb.Eval($vbcode)
}
Execute command example -
PS> Invoke-VbScript -exe 'msgbox("hi")'
Evaluate expressions and return result example -
PS> $name=Invoke-VbScript 'InputBox("Enter your name","Test")'
Have fun!
Just saw that VRMCplus that I wrote about earlier has been updated to v1.6. Get it here.
The changes are (taken from this blog post)
So what is new in 1.6.0?
First of all, the UI reflects Virtual Server terminology. Both Paul and I had used a mix of Virtual Server terminology and internal (SDK) terminology. To reflect the terminology used in the web administration UI of Virtual Server, the terminology of VMRCplus has been updated.
Second, VMRCplus now offers configuration of scripts on both the Virtual Server and Virtual Machine level. This was missing from the previous release.
Third, VMRCplus offers configuring promiscuous mode on the network so you can trace traffic in the virtual switch. This is something Virtual Server does not offer in the web administration UI.Of course there have been minor enhancements like storage of Console Manager coordinates, conflict handling when a shortcut already exists (something Virtual Server fails to resolve).
The COM and LPT port assignment logic has been fixed (most of it did not work).
The x86 installer package no longer installs on x64. This has been done to prevent issues with 32-bit VMRCplus on 64-bit Virtual Server.Error handling has been enhanced and several issues have been fixed.
I managed to meet MOW at Ask-the-Experts today. MOW is famous within the PowerShell community for his PowerTab function and he is running thepowershellguy.com blog.
If you haven't done so already - get a copy of Powertab now!
Well, it was fun meeting him and discuss some of the features I'm missing. On is -
An I gave my regards for PowerTab as such and the new constructor feature - try it yourself -
Anyway, the PowerShell v2 CTP enables him to do a full tokenizing of the command line, so even better intelligence will be possible.
Marketing is a strange beast. Server virtualization in Windows Server 2008 - e.g. the replacement of Virtual Server - will be called Hyper-V. I already hate that name! HyperV perhaps - but why the hyphen??
Anyway, Hyper-V will be a server feature that can be turned on. Microsoft is also planning a Hyper-V Server SKU.
Hyper-V is still expected to be delivered 6 months after Windows Server 2008.
On the management side, it was demoed at the keynote here in Barcelona, a virtual server manager that could manage Virtual Server 2005, Hyper-V *and* WMware server!
(I apologize for these reposts. Windows Live Writer does not seem to be able to edit posts!?)
This is the first time I'm using the released Windows Live Writer to post here, so bear over with me if it does not work as expected ;) The new Windows Live Writer seems to support pictures and formatted PowerShell scripts, so it is much better than using the webpage.
In this year's Teched IT-Forum I'm going to focus on Windows Server 2008 and the System Center products - most ConfigMgr and OpsMgr. And then this is going to be a great PowerShell week. The CTP of V2 has been released and I hope to get in touch with some of the PowerShell staff as I have about 45 things I would like to discuss with them. I also hope to get in touch with some of the other people from the community.
# Construct an array
$array=1,2,3
# Pass the array down the pipeline
# Gettype will be called 3 times for each integer
# in the array
$array | cm gettype
IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True True Int32 System.ValueType
True True Int32 System.ValueType
True True Int32 System.ValueType
# Wrap array with the array operator. This changes
# nothing as the array operator only creates an array
# if there is none
@($array) | cm gettype
IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True True Int32 System.ValueType
True True Int32 System.ValueType
True True Int32 System.ValueType
# Pass an array with the first argument being our
# array - this works
,$array | cm gettype
IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True True Object[] System.Array
# Use the updated Call-Method and use the InputObject
# argument - like the one found on Get-Member
cm gettype -InputObject $array
IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True True Object[] System.Array
## This is the updated Call-Method function
function Call-Method($method,$InputObject) {
begin {
if ($inputObject) {
$m=$inputObject.$method
$m.invoke($args)
}
}
process {
if ($_) {
$m=$_.$method
$m.invoke($args)
}
}
}
new-alias -force cm Call-Method
function Call-Method($method) { process { $m=$_.$method; $m.invoke($args) } }
new-alias -force cm Call-Method
Last night Inceptio received the Microsoft Unified Communications Partner of the year award ;-)
Basically there are two Client licenses that are additative. You always need a Standard CAL and can on top of that buy an Enterprise CAL that deliveres all of the Conferencing (Web, Audio/Video, Application Sharing) and the VoIP & Remote Call Control features.
For the servers there's the Standard and Enterprise Edition (Scalability and Availability) and you should note that Communicator Web Access, Speech Server 2007 and Office Communicator Mobile 2007 are included in the server licensec.
Update - find more information on licensing options on the web page How to buy Microsoft Office Communications Server 2007.
For pricing information according to Michael Dunn's posting regarding Speech Server 2007 pricing it will be -
No info from Dunn though on the licensing type / price (MVLS, Select etc.)
<Types>
<Type>
<Name>System.IO.FileInfo</Name>
<Members>
<ScriptProperty>
<Name>DatePictureTaken</Name>
<GetScriptBlock>
trap {write-debug $error[0]}
$null=[reflection.assembly]::loadfile("$env:windir\Microsoft.Net\framework\v2.0.50727\System.Drawing.Dll")
$shell=new-object -com Shell.Application
$folder=$shell.Namespace((split-path $this))
foreach($i in 1..100) {
if ($folder.GetDetailsOf("",$i) -eq "date picture taken") {write-debug $i;break}
}
if ($i -lt 100) {
$folder.items() | ? { $_.name -eq $this.name } | % {
$date=$folder.GetDetailsOf($_,$i)
if ($date) {
# Dates are text and DD-MM-YYYY cannot be converted to datetime
# Convert DD-MM-YYYY to YYYY-MM-DD
$date=$date -replace "^(\d{2})\-(\d{2})\-(\d{4})",'$3-$2-$1'
# Cast to a datetime
[datetime] $date
}
}
}
</GetScriptBlock>
</ScriptProperty>
</Members>
</Type>
</Types>
If you make any improvements, please post them as comments.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
These are similar to the requirements that are imposed on OCS TAP customers - but new is of course actual public support for SP1 Beta 2 on the UM role.
Btw. if you want more info on Exchange 2007 UM and OCS integration then take a look at Introducing Unified Messaging in Office Communications Server 2007 environment.
Continuing on my earlier post there's a press release from Microsoft on the Technology Preview program on SP1 Beta 2. As the press release states it now includes -
Support for Windows Server 2008 and Windows Vista®. Exchange Server 2007 SP1 runs on Microsoft’s next-generation server platforms, including Windows Server 2003 SP2 and Windows Server 2008. The update also enables Exchange Server 2007 management tools to run on Windows Vista and Windows Server 2008. Among other benefits, Windows Server 2008 clustering will make it easier for companies to deploy geographically dispersed Exchange Server clusters.
Enhanced integration with Office Communications Server 2007. Exchange Server 2007 unified messaging goes beyond e-mail to deliver faxes and voice mail to Outlook. With Exchange Server 2007 SP1, people can retrieve voice mail messages from Microsoft Office Communicator 2007 with a single click. Also, certain Office Communications Server 2007- and Office Communicator 2007-qualified devices will be able to work with Exchange Server 2007 for additional functionality, such as a new message indicator that shows when a user has a new voice mail message.
Additional Exchange ActiveSync® policies. New Exchange ActiveSync policies in SP1 build on Exchange Server 2007’s robust security and management features with new policies for synchronization, authentication and encryption. For businesses with more advanced data protection needs, Exchange Server 2007 SP1 offers device, network and application controls. These new features allow network administrators to help manage and secure Exchange ActiveSync-enabled mobile devices.
Standby Continuous Replication (SCR). This new high-availability feature helps organizations recover quickly from failures that affect an entire datacenter, such as a natural disaster or extended power outage. Mailbox data is replicated continuously to a standby server using Exchange Server’s built-in log file shipping technology. The standby server can be quickly activated if the primary server or datacenter goes offline.
Enhanced security. Microsoft also unveiled Forefront™ Security for Exchange Server SP1, which integrates with Exchange Server 2007 SP1 to provide an extra layer of security for even greater protection and control. Forefront Security for Exchange Server includes multiple scan engines from industry-leading security firms integrated in a single solution to help protect against viruses, worms and spam. The new service pack for Forefront Security for Exchange Server features improvements in content filtering and manageability as well as support for Windows Server 2008.
Find the rest here.
I ran into a documentation error in the dbexpimp.exe suppport tool/help file included with OCS 2007. It states that the syntax for import is dbimpexp.exe /hrxmlfile:"c:\SavedUserData.xml". It's obviously "dmpimpexp.exe /import /hrxml...."
The other issue was a bit more quirky. After reinstalling the OCS 2007 Front End I reassigned all users from ADUC to the new RTM server (With the same name as the old). After that I imported the user data using dbimpexp.exe and everything worked fine (Presence, IM, voice and conferencing). While upgrading the Mediation Server I noticed that all users where disabled, but since all users worked and I was running a RC version of the MMC from the Mediation Server I concluded it was a co-existence issue.Wainhouse research has released the results of a survey that shows Microsoft leads the Unified Communications race at small and large customers (160 end users where asked) -
Survey responses indicate that Microsoft has a commanding lead in the enterprise unified communications space with 48% of those surveyed stating that they are currently using or considering to use Microsoft OCS within their organization as compared to 35% currently using or considering to use Cisco UPC and 24% currently using or considering to use IBM Lotus Sametime.
In line with what we see at customers and partners it also states that "One surprising statistic is the huge mindshare Microsoft has generated over all other unified communications solutions."
Microsoft is not only a genius at marketing, personally I think that Office Communications Server 2007 and the accompanying line of products (See Just how big is the OCS release?) is the most interesting release of products from Microsoft since Exchange 4.0 was shipped more than 11 years ago back in March 1996 (See my blog Microsoft Exchange's 10 year anniversary).
See the full Press release here.
I received the following mail today stating -
Dear TAP Participant,
This is the update that all you (and of course all of us here at UC) have been waiting for: Microsoft Office Communications Server (OCS) 2007, Microsoft Office Communicator (MOC) 2007, Live Meeting (LM) console (2007), Outlook Add-Ins, Voice devices including “Tanjay,” “Catalina,” “Anacapa” and Microsoft® RoundTable™ have reached the Release to Manufacturing (RTM) milestone!
$input | % { "$(get-date -f HH:mm:ss) $(out-string -inp $_)"}
process {"$(get-date -f HH:mm:ss) $(out-string -inp $_)"}
PS> "hi" | .\Add-TimestampA.ps1
10:08:05 hi
PS> "hi" | .\Add-TimestampB.ps1
10:08:06 hi
PS> "a","b","c" | .\Add-TimestampA.ps1
10:09:01 a
10:09:01 b
10:09:01 c
PS> "a","b","c" | .\Add-TimestampB.ps1
10:09:03 a
10:09:03 b
10:09:03 c
PS> "a","b","c" | % { start-sleep -s 3; $_ } | .\Add-TimestampA.ps1
10:10:11 a
10:10:11 b
10:10:11 c
PS> "a","b","c" | % { start-sleep -s 3; $_ } | .\Add-TimestampB.ps1
10:10:21 a
10:10:24 b
10:10:27 c
Downsides -
The note below
When browsing to https://204.176.46.35/ IE gives a warning that the certificate does not match - but you cannot view the certificate. Continuing by clicking the red shield returns a 403 error - and again you cannot view the certificate. A shame. With Wireshark I could capture the TLSv1 Server Hello package and see the certificate CN which reads:
id-at-commonName=*.sharedview.com,
id-at-organizationalUnitName=Microsoft.com,
id-at-organizationName=Microsoft.com,
id-at-localityName=Redmond,
id-at-stateOrProvinceName=WA,
id-at-countryName=US
So I guess it is a real Microsoft server.
I have used a lot of time educating my grandma (who is >80 years old) on how to use the Internet, Live Messenger and her Webcam (Which she called me last summer to request "Can I also get one of those camera thingies that your children have").
Luckily she listened to me, because today she called me that she was getting strange messages from her family members on Live Messenger (Soon 24 great-grandchildren in total).
So if you receive a message from one of you Live Messenger contacts saying "look at my summer pictures http_//paulina2k8.tripod.com/summer2008.zip" then DON´T click the link.
If one of your friends downloaded the file, it will also try to do file transfers of files called "images052.zip", "photo9.zip", "album29.zip" and others to your computer (And to all of your buddies if you are stu... enough to transfer and open the file). In this case it actually also wrote "Hey, acceptera mina bilder" and other messages in Swedish from her daughter based in Sweden (We are from Denmark).
There are no hits on Live Search and only a few on Google so it´s appears to be a fairly new variant.
I actually recently wrote a security whitepaper on Office Communications Server 2007 security explaining and showing the dangers in using Public IM and VoIP clients generally and especially in businesses (Honestly anywhere if you are not well educated IT Pro ... or my grandma ;-) and this again shows that IM is a fantastic tool but not without associated security issues.
Well this was just a short warning ... the hot chocolate and buns are waiting for me.
I will be back with more content when OCS 2007 has been officially RTM'ed !
param([switch]$nameOnly)
$ds=[system.directoryservices.directorysearcher] "(&(objectCategory=serviceConnectionPoint)(cn=MS Virtual Server))"
$servers=$ds.findall()
if ($nameOnly) {
$servers | % { $_.path.split("=,")[3] }
}
else {
$servers
}
Give it a spin!
Quick note - If you only want to read one (very large) whitepaper on Exchange then look at Technical Architecture of Exchange Server 2007 and skip the rest ;-)