MoveSysvol – Automate the relocation of the Sysvol folder (DFSR Version)

MoveSysvol (DFSR version) automated by Shaun Vermaak is a batch to automatically relocate the Sysvol folder as per https://technet.microsoft.com/en-us/library/cc816594(v=ws.10).aspx

The following must be in the working folder or in path:
MoveSysvol.bat
SetDFSR.vbs
sysvol.inf

UPDATE: Please ensure that all DCs are in the default Domain Controllers OU

Usage: MoveSysvol.bat OLDSYSVOLPATH NEWSYSVOLPATH DOMAINFQDN
Example: MoveSysvol.bat C:WindowsSYSVOL D:SYSVOL TESTDOMAIN.COM

Attachment(s):
[list-attachments]

Unable to create folder on drive mapped to share with ABE enabled

Struggled for a bit with Windows 7 computers that could not create folders on mapped drives via Explorer. Doing the same via command prompt creates the folder successfully.

Turns out that ABE, which was setup correctly, was causing the issue and that themaids on http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2012/Q_28509884.html had the same issue.

Weird enough you give Domain Users read/execute, List folder contents, and read permissions and instantly the Windows 7 clients can create folders again and, best of all, ABE is still working

BizTalk – Publishing Message Transformation Orchestration as WCF Web Service

The following details the steps required to publish a very simple message transformation orchestration as a WCF web service via BizTalk

 

Part 1 – Project

1

1) Open Visual Studio and create an “Empty BizTalk Server Project”

 

 

2

2) Right click project in Solution Explorer and select “New item…”

 

 

3

3) Add a “Schema” file that will be used to define the request message

 

 

4

4) Define the request message schema. The schema in example has two attributes, “Amount” and “Quantity”. Define namespace.

 

 

5

5) Repeat step 2 and add another “Schema” for the response message. In this example it has one attribute called “Tax”. Define namespace.

 

 

6

6) Repeat step 2 and add a “Map”

 

 

7

7) In map the transformation is defined from a request message to a response message.

 

 

8

8) Values for the first “Mathematical Functoid”

 

 

9

9) Values for the second “Mathematical Functoid”

 

 

10

10) Right-Click map and select “Test Map”

 

 

11

11) CTRL-Click the first test map to see test request map

 

 

 

12

12) CTRL-Click the second test map to see response map with value calculate from test request map

 

 

13

13) Repeat step 2 and add an “Orchestration”

 

 

14

14) Add a “Receive Shape”,  “Transform Shape” and a “Send Shape”. Create a two messages, one for a request schema and another for the response schema.

 

 

15

15) Configure the “Transform Shape” with the map created in step 6.

 

 

16

16) Add port and give it a name.

 

 

17

17) Create a new port type and give it a name. The port must be public and a request-response pattern.

 

 

18

18) Leave at “Specify later”.

 

 

19

19) Configure messages in the “Receive Shape” and “Send Shape” from the messages created in step 14.

 

 

20

 

20) Connect the “Request” and “Response” ports to the “Receive Shape” and the “Send Shape”. Set the orchestration to public.

 

 

21

 

21) Specify the BizTalk application name otherwise it will deploy in default application on BizTalk.

 

 

22

 

22) Add a key to sign assembly. Assembly will be GAC deployed and a key file is required.

 

 

 

23

 

23) Build solution

 

 

24

 

24) Deploy solution

 

 

25

 

25) GAC deploy assembly after each build

 

Part 2 – Publish

p1

 

1) Start the “BizTalk WCF Publishing Wizard”.  In this example the “WCF-WSHttp” transport type is used. Ensure that “Enable on-premise metadata exchange” and “Create BizTalk receive locations in the following application:” has the application published in part 1 selected.

 

 

p2

2) Select “Publish BizTalk orchestrations as WCF service”.

 

 

p3

 

3) On the next page browse to the assembly created in part 1.

 

 

p4

 

4) Ensure ports are shown

 

 

 

p5

 

5) Specify namespace

 

 

p6

 

6) In this example the WCF service will allow anonymous access.

 

 

p7

 

7) If we at this stage browse to web service location we get this error.

 

 

p8

 

8) To resolve error in step 2, change the identity of the application pool used by the web service, to one with appropriate BizTalk rights.

 

 

p9

 

9) If we at this stage browse to web service location we get this error.

 

 

p10

 

10) To resolve error in step 9, configure the orchestration in the published BizTalk application.

 

 

p11

 

11) Start the BizTalk application.

 

 

p12

 

12) After these step, the web service test page should display correctly.

 

Part 3 – Testing

t1

After the orchestration is published, it is available and transformation can be tested

Test Passwords Against Active Directory User

Tool to test password against Active Directory user. Multiple passwords can be tested by ; separating them

Usage: CheckCredentials.exe FQDN USERNAME PASSWORD1[;PASSWORD2;PASSWORD3..]

[sourcecode language=”vb”]
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.DirectoryServices.AccountManagement;
using System.Diagnostics;

namespace CheckCredentials
{
class Program
{
static void Main(string[] args)
{
if (args.GetUpperBound(0) == 2)
{
foreach (string password in args[2].Split(‘;’))
{
using (PrincipalContext pc = new PrincipalContext(ContextType.Domain, args[0]))
{

// validate the credentials
bool isValid = pc.ValidateCredentials(args[1], password);

if (isValid)
{
Console.WriteLine(@"{1}@{0} has password {2}", args[0], args[1], password);
}

}
}
}
else
{
Console.WriteLine("Usage:{0} FQDN USERNAME PASSWORD1[;PASSWORD2;PASSWORD3..]", Process.GetCurrentProcess().ProcessName + ".exe");
}
}
}
}
[/sourcecode]

Attachment(s): [list-attachments]

View Shaun Vermaak's profile on LinkedIn

Fixed drive letter in WinPE

This script can be added to a WinPE environment to ensure that the removable boot media always have a specific drive letter.

All you need to do is create a file called “72821acd-379a-478a-a2c6-1ebd72cbead5.txt” on the media that you want to have a fixed drive letter, in this example drive letter M is assigned. After this add the script as a startup script into your PE boot media.

[sourcecode language=”vb”]
Option Explicit

Dim objWMIService
Dim objFileSystemObject
Dim colVolumes
Dim objVolume

Set objWMIService = GetObject(“winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2”)
Set objFileSystemObject = CreateObject(“Scripting.FileSystemObject”)

Set colVolumes = objWMIService.ExecQuery(“Select * from Win32_Volume”)
For Each objVolume in colVolumes
If objFileSystemObject.FileExists(objVolume.DriveLetter & “\72821acd-379a-478a-a2c6-1ebd72cbead5.txt”) Then
objVolume.DriveLetter = “M:”
objVolume.Put_
End If
Next
[/sourcecode]

Attachment(s): [list-attachments]