Microsoft | My MS World

MS-DOS 1.1,2.0 and MS Word for windows 1.1 sources have been released!

by Karl Bustamante | Mar 27, 2014 | Microsoft, News

MS-DOS

I just read that source code of MS-DOS and Word were released today.

This is a good thing to better understand how it all started at Microsoft!

Here are the articles :

Change Voice Policy of Lync 2013 Response Group Workflow, Dialin, or any other service

by Karl Bustamante | Mar 27, 2014 | Lync 2010, Lync 2013, Powershell

There is two ways to change the Voice Policy with Lync 2013.

CmdLets
Active Directory (advanced)

First of all, we will se how to get the Voice Policy from an Application Endpoint (Workflow, Dialin etc…) :

Get-CsApplicationEndpoint -Identity "*WorkflowName*" | Select VoicePolicy
Get-CsApplicationEndpoint -Identity "*WorkflowName*" | FL *

1 2	Get-CsApplicationEndpoint -Identity "WorkflowName" \| Select VoicePolicy Get-CsApplicationEndpoint -Identity "WorkflowName" \| FL *

So if you want to change the voice Policy of a Workflow with powershell, here is the cmdlet :

Get-CsApplicationEndpoint -Identity "*WorkflowName*" | GrantCsVoicePolicy -PolicyName "VPolicy-US-International"

1	Get-CsApplicationEndpoint -Identity "WorkflowName" \| GrantCsVoicePolicy -PolicyName "VPolicy-US-International"

Now we are going to be more “serious” by going to make changes in the Active Directory for the workflow itself.

First, depending on your environment, the RTC services folder can be found in different paths:

[Configuration]/Services/RTC Services/Application Contacts
[Domain Naming Context]/Services/Microsoft/RTC Services/Application Contacts

Once you’re in the path, search for the Active Directory Contact object that is your workflow, and modifies the attribute of msRTCSIP-UserPolicies.

It may have some entries like “0=123,1=6,7=2,…”

The “7=” is the voice Policy pointer. So to assign the correct voice Policy number to the Contact, Show the anchors of the voice policies in powershell and add it to the contact.

Powershell Voice Policy Anchor :

Get-CsVoicePolicy | select Anchor

1	Get-CsVoicePolicy \| select Anchor

This is working for all the policies.

Karl

Disable Close button in Powershell Window

by Karl Bustamante | Mar 25, 2014 | Powershell

I did some powershell scripting these days.

Disabled Window running script

Someone asked me if it would be possible to avoid the user to close the powershell window while a script is running (logon or any other). After a few searches in the MSDN world, I was able to handle the window and send some parameters to it.

For this, I ask the user32.dll Library to disable the powershell window and to disable the button (close menu). To remove any undesired button, I set the Windows style to Toolbox.

I know the fact of disabling window will avoid any user input and click on any button, but as they asked me to disable the button, I dit it this way. So use the rest as know-how… 🙂

Knowing what I need to code, I will use some user32.dll methods :

GetSytemMenu
EnableMenuItem
SetWindowLongPtr
EnableWindow

Hope that this script can be useful to some admins!

Karl

Windows versions tested
Windows 2000	–
Windows XP	–
Windows 7	OK
Windows 8	–
Windows 8.1 Standard	OK (Disabled window only)

Here is the script :

#Calling user32.dll methods for Windows and Menus
$MethodsCall = '
[DllImport("user32.dll")] public static extern long GetSystemMenu(IntPtr hWnd, bool bRevert);
[DllImport("user32.dll")] public static extern bool EnableMenuItem(long hMenuItem, long wIDEnableItem, long wEnable);
[DllImport("user32.dll")] public static extern long SetWindowLongPtr(long hWnd, long nIndex, long dwNewLong);
[DllImport("user32.dll")] public static extern bool EnableWindow(long hWnd, int bEnable);
'

#Create a new namespace for the Methods to be able to call them
Add-Type -MemberDefinition $MethodsCall -name NativeMethods -namespace Win32

#WM_SYSCOMMAND Message
$MF_GRAYED = 0x00000001L    #Indicates that the menu item is disabled and grayed so that it cannot be selected.
$MF_BYCOMMAND = 0x0               #Gives the identifier of the menu item. If neither the MF_BYCOMMAND nor MF_BYPOSITION flag is specified, the MF_BYCOMMAND flag is the default flag.            
$MF_DISABLED = 0x00000002L #Indicates that the menu item is disabled, but not grayed, so it cannot be selected.
$MF_ENABLED = 0x00000000L #Indicates that the menu item is enabled and restored from a grayed state so that it can be selected.
#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms647636(v=vs.85).aspx

$SC_CLOSE = 0xF060
$SC_CONTEXTHELP = 0xF180
$SC_MAXIMIZE = 0xF030 
$SC_MINIMIZE = 0xF020 
$SC_TASKLIST = 0xF130
$SC_MOUSEMENU = 0xF090
$SC_KEYMENU = 0xF100
#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms646360(v=vs.85).aspx

$GWL_EXSTYLE = -20
$GWL_STYLE = -16
#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms644898(v=vs.85).aspx

#WM_SETICON Message  -  http://msdn.microsoft.com/en-us/library/ms632643%28VS.85%29.aspx
$WM_SETICON = 0x0080;
$ICON_SMALL = 0;
$ICON_BIG = 1;

#Extended Window Styles
$WS_EX_DLGMODALFRAME = 0x00000001L
$WS_EX_NOACTIVATE = 0x08000000L
$WS_EX_TOOLWINDOW = 0x00000080L
$WS_EX_STATICEDGE = 0x00020000L
$WS_EX_WINDOWEDGE = 0x00000100L
$WS_EX_TRANSPARENT = 0x00000020L
$WS_EX_CLIENTEDGE = 0x00000200L
$WS_EX_LAYERED = 0x00080000
$WS_EX_TOPMOST = 0x00000008L
#... http://msdn.microsoft.com/en-us/library/windows/desktop/ff700543(v=vs.85).aspx

#Get window handle of Powershell process (Ensure there is only one Powershell window opened)
$PSWindow = (Get-Process Powershell) | where {$_.MainWindowTitle -like "*Powershell*"}
$hwnd = $PSWindow.MainWindowHandle

#Get System menu of windows handled
$hMenu = [Win32.NativeMethods]::GetSystemMenu($hwnd, 0)

#Window Style : TOOLWINDOW
[Win32.NativeMethods]::SetWindowLongPtr($hwnd, $GWL_EXSTYLE, $WS_EX_TOOLWINDOW) | Out-Null

#Disable X Button and window itself
[Win32.NativeMethods]::EnableMenuItem($hMenu, $SC_CLOSE, $MF_DISABLED) | Out-Null
[Win32.NativeMethods]::EnableWindow($hwnd, 0) | Out-Null

Write-Host "Disabled!" -ForegroundColor Red 
sleep 5

#Enable X Button
[Win32.NativeMethods]::EnableMenuItem($hMenu, $SC_CLOSE, $MF_ENABLED) | Out-Null
[Win32.NativeMethods]::EnableWindow($hwnd, 1) | Out-Null

Write-Host "Enabled!" -ForegroundColor Green
sleep 2

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

#Calling user32.dll methods for Windows and Menus

$MethodsCall = '

[DllImport("user32.dll")] public static extern long GetSystemMenu(IntPtr hWnd, bool bRevert);

[DllImport("user32.dll")] public static extern bool EnableMenuItem(long hMenuItem, long wIDEnableItem, long wEnable);

[DllImport("user32.dll")] public static extern long SetWindowLongPtr(long hWnd, long nIndex, long dwNewLong);

[DllImport("user32.dll")] public static extern bool EnableWindow(long hWnd, int bEnable);

'

#Create a new namespace for the Methods to be able to call them

Add-Type -MemberDefinition $MethodsCall -name NativeMethods -namespace Win32

#WM_SYSCOMMAND Message

$MF_GRAYED = 0x00000001L #Indicates that the menu item is disabled and grayed so that it cannot be selected.

$MF_BYCOMMAND = 0x0 #Gives the identifier of the menu item. If neither the MF_BYCOMMAND nor MF_BYPOSITION flag is specified, the MF_BYCOMMAND flag is the default flag.

$MF_DISABLED = 0x00000002L #Indicates that the menu item is disabled, but not grayed, so it cannot be selected.

$MF_ENABLED = 0x00000000L #Indicates that the menu item is enabled and restored from a grayed state so that it can be selected.

#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms647636(v=vs.85).aspx

$SC_CLOSE = 0xF060

$SC_CONTEXTHELP = 0xF180

$SC_MAXIMIZE = 0xF030

$SC_MINIMIZE = 0xF020

$SC_TASKLIST = 0xF130

$SC_MOUSEMENU = 0xF090

$SC_KEYMENU = 0xF100

#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms646360(v=vs.85).aspx

$GWL_EXSTYLE = -20

$GWL_STYLE = -16

#... http://msdn.microsoft.com/en-us/library/windows/desktop/ms644898(v=vs.85).aspx

#WM_SETICON Message - http://msdn.microsoft.com/en-us/library/ms632643%28VS.85%29.aspx

$WM_SETICON = 0x0080;

$ICON_SMALL = 0;

$ICON_BIG = 1;

#Extended Window Styles

$WS_EX_DLGMODALFRAME = 0x00000001L

$WS_EX_NOACTIVATE = 0x08000000L

$WS_EX_TOOLWINDOW = 0x00000080L

$WS_EX_STATICEDGE = 0x00020000L

$WS_EX_WINDOWEDGE = 0x00000100L

$WS_EX_TRANSPARENT = 0x00000020L

$WS_EX_CLIENTEDGE = 0x00000200L

$WS_EX_LAYERED = 0x00080000

$WS_EX_TOPMOST = 0x00000008L

#... http://msdn.microsoft.com/en-us/library/windows/desktop/ff700543(v=vs.85).aspx

#Get window handle of Powershell process (Ensure there is only one Powershell window opened)

$PSWindow = (Get-Process Powershell) | where {$_.MainWindowTitle -like "*Powershell*"}

$hwnd = $PSWindow.MainWindowHandle

#Get System menu of windows handled

$hMenu = [Win32.NativeMethods]::GetSystemMenu($hwnd, 0)

#Window Style : TOOLWINDOW

[Win32.NativeMethods]::SetWindowLongPtr($hwnd, $GWL_EXSTYLE, $WS_EX_TOOLWINDOW) | Out-Null

#Disable X Button and window itself

[Win32.NativeMethods]::EnableMenuItem($hMenu, $SC_CLOSE, $MF_DISABLED) | Out-Null

[Win32.NativeMethods]::EnableWindow($hwnd, 0) | Out-Null

Write-Host "Disabled!" -ForegroundColor Red

sleep 5

#Enable X Button

[Win32.NativeMethods]::EnableMenuItem($hMenu, $SC_CLOSE, $MF_ENABLED) | Out-Null

[Win32.NativeMethods]::EnableWindow($hwnd, 1) | Out-Null

Write-Host "Enabled!" -ForegroundColor Green

sleep 2

Get-CsActiveCalls – Get Lync Mediation server active calls with powershell

by Karl Bustamante | Jan 7, 2014 | Lync 2010, Lync 2013

Hi,

This is a simple script you can use to see which server has active calls (mediation).

This uses the Get-CsWindowsService cmdlet to get the RTCMEDSRV values. This can be useful if you need to restart a server.

If you need only one server, you can also use this command :

Get-CsWindowsService -Name RTCMEDSRV | select activitylevel

To launch the function, just write the function name followed by the computername :

Get-CsActiveCalls computer01,computer02,computer03,computer04

This will show you the active calls like in the picture.

A few modifications : powershell seems to keep all values from before, so we just clear the values after showing the object with Clear-Item.

Communication Server versions tested
Office Communication Server 2007	–
Microsoft Lync Server 2010	OK
Microsoft Lync Server 2013	OK

Here is the script :


function Get-CsActiveCalls {
	param (
        [parameter(Mandatory=$false)][array]$Computer = $env:computername
    )
 	$BeforeErrorActionPreference=$ErrorActionPreference
	$BeforeProgressPreference = $ProgressPreference

	$ErrorActionPreference="SilentlyContinue"
	$ProgressPreference = "SilentlyContinue"
	cls
	
	$DateTimeDone = (Get-Date).tostring()
	Write-Host "Calls state on " -NoNewline
	Write-Host $DateTimeDone -ForegroundColor Green
	
    foreach ($PC in $Computer) {
 
        $x = Get-CsWindowsService -Name RTCMEDSRV -ComputerName $PC | select -expandproperty activitylevel
        
		$obj = New-Object PSObject
        $obj | Add-Member NoteProperty "Computer" $PC #.ToString()
 
        $findOut = $x -match '.*Current Outbound Calls=(\d+),.*'
        if ($findOut) {
            $outbound = $matches[1]
            $obj | Add-Member NoteProperty "Outbound Calls" $outbound #.ToString()
        }
 
        $findIn = $x -match '.*Current Inbound Calls=(\d+),.*'    
        if ($findIn) {
            $inbound = $matches[1]
            $obj | Add-Member NoteProperty "Inbound Calls" $inbound #.ToString()
        }
		
		$obj
    }
	
	Clear-Item $matches
	Clear-Item $obj
	Clear-Item $x
	Write-Host "Press any key to continue ..." -ForegroundColor yellow
	$KeyDown = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
	
	$ErrorActionPreference=$BeforeErrorActionPreference
	$ProgressPreference=$BeforeProgressPreference
}
Get-CsActiveCalls computer01,computer02,computer03,computer04

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

function Get-CsActiveCalls {

param (

[parameter(Mandatory=$false)][array]$Computer = $env:computername

)

$BeforeErrorActionPreference=$ErrorActionPreference

$BeforeProgressPreference = $ProgressPreference

$ErrorActionPreference="SilentlyContinue"

$ProgressPreference = "SilentlyContinue"

cls

$DateTimeDone = (Get-Date).tostring()

Write-Host "Calls state on " -NoNewline

Write-Host $DateTimeDone -ForegroundColor Green

foreach ($PC in $Computer) {

$x = Get-CsWindowsService -Name RTCMEDSRV -ComputerName $PC | select -expandproperty activitylevel

$obj = New-Object PSObject

$obj | Add-Member NoteProperty "Computer" $PC #.ToString()

$findOut = $x -match '.*Current Outbound Calls=(\d+),.*'

if ($findOut) {

$outbound = $matches[1]

$obj | Add-Member NoteProperty "Outbound Calls" $outbound #.ToString()

}

$findIn = $x -match '.*Current Inbound Calls=(\d+),.*'

if ($findIn) {

$inbound = $matches[1]

$obj | Add-Member NoteProperty "Inbound Calls" $inbound #.ToString()

}

$obj

}

Clear-Item $matches

Clear-Item $obj

Clear-Item $x

Write-Host "Press any key to continue ..." -ForegroundColor yellow

$KeyDown = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")

$ErrorActionPreference=$BeforeErrorActionPreference

$ProgressPreference=$BeforeProgressPreference

}

Get-CsActiveCalls computer01,computer02,computer03,computer04

Lync Server 2010 – Beep before call

by Karl Bustamante | Feb 14, 2013 | Lync 2010

Hi all,

As per usual, this is a network issue. You can use Microsoft Network Monitor with port and IP filters to check connexions.

Normally, the issue is the following :

The client is making an outbound call, the call has 3 ways to process and will try the ways as follow :

Internet (Edge) – The call ask the EDGE if someone with the following sip is connected trough him.
PSTN – Your PSTN Gateway
Voicemail – Your UM Exchange server

For any network reason (Switch, Router,Firewall,…), the client can reach the edge, but the edge can’t reach the client. This is causing several beeps before the call really begin.

Hope this helps!

Beeps before Lync call

by Karl Bustamante | Nov 6, 2012 | Lync 2010