MSMQ and reseal ?

[Henrik]

Hi,

After running fbreseal.exe the MSMQ -services are not running anymore.
They are set to automatic (startup) and all dependencies for running are ok.
I can start them (MSMQ + trigger) manualy and they start to run ok.

Before running fbreseal.exe i verify that they are ok. One or more reboots
do not change this.
I have tried with fbreseal.exe -keepuser without success.
The system Cloning tool is set to : UnJoin Domain and Remove Mounted
devices= TRUE, else FALSE.

I have SP2.

Any ideas,

Henrik.

 

[Robert]

Henrick,

This is the same issue that Desi from Tyco was having
the other day. You need to go into the System Cloning
Tool component advanced settings and change the
cmiRemoveUserSettings to False. This should fix the
issue. I believe anything you do at a command prompt with
FBReseal cmd will be trumped by the settings in the System
Cloning Tool Component.

Robert

 

[Desi]

Actually, my issue turned out to be something completely different.
There's a long thread about it in this group.

I have seen this occur, however; The solution for me was to run the
following commands after the system reboots following fbreseal:

msdtc -install
msdtc -resetlog

For some reason, fbreseal seems to hit the MSDTC service, which MSMQ
relies upon. The commands above reinstall the MSDTC service, and MSMQ
works fine after that.

There are several other threads about this - do a search in the group
and you'll find them.

Desi

 

[KM]

From XPe Rel.Notes:
a..
a.. Cloning process (i.e. SysPrep) fails to restart MSDTC service when other services have started or are starting. Workaround:
issue the following commands after cloning completes, in order to restart MSDTC and IIS:
a.. msdtc -install -a
b.. msdtc -resetlog
c.. iisreset /restart

 

[Desi]

Thanks, KM.

I wasn't at my desk and couldn't remember the full instructions, which
is why I suggested that he do a search.
I guess that's why you get paid the big bucks

Desi

 

[Henrik]

Hi,

Thanks for answers.

miRemoveUserSettings is set to false in the System Cloning Tool..

However, after I run fbreseal (and power down), i clone the disk.
From here on i don't have a chance to run any program i startup the first
time.
I have to be sure the the MSMQ is running after the first boot, without any
program to be executed.

Is this possible ?.

Henrik.

 

[KM]

Henrik,

However, after I run fbreseal (and power down), i clone the disk.
From here on i don't have a chance to run any program i startup the first time.
I have to be sure the the MSMQ is running after the first boot, without any
program to be executed.

Is this possible ?.

Unless you want to switch to newsid approach to replace fbreseal (but be aware that newsid has known bugs) you don't have a choice
since that is a bug of fbreseal (or MSDTC).
So, I guess, you are left with the workaround from XPE Rel.Notes.

What is the problem to launch an app on the first boot after cloning?
There is million ways to implement that but you please tell us your restrictions.

 

[Henrik]

Hi,

I guess there is no way around a post-clone bat-file, handling MSDTC and
MSMQ restarts.

The reason for not having a post-clone program, was just to ease the
installation.
I will make a bat-file that stops the MSMQ and MSDTC services, and then
starts them again.
The bat-file will be placed in the startup-folder. The bat-file deletes
itself after running..
I guess this is one way to do it. It works.

Thanks for all help.

Henrik.

Henrik,


Unless you want to switch to newsid approach to replace fbreseal (but be

aware that newsid has known bugs) you don't have a choice

 

[David D]

Here is another thing.
I ran into a situation with MSMQ using the computer name.
We entered 127.0.0.1 but it resolves to the computer name.
After cloning, we change the computer name and then the MSMQ does not work.
Not sure if you have the same issue but as you know you can make fbreseal
give your cloned image a random computer name.
I don't use this feature and have a custom application assign a computer
name based on the MAC but nontheless, when we change the computer name, the
MSMQ trigger was not working. We fix this by having our application hack at
the registry settings for that MSMQ to assign it to the current computer
name.

 

[RoyH]

David D,

The grouop archive would benefit if you could post the registry hack
for redefining the Computername used by MSMQ.

Thanks, Roy

 

[David D]

For our specific issue here was our VB code to fix:
Registry entry was easy to find, we changed the computer name then searched
the registry for our previous computer name to find the registry entry.
Public Sub UpdateMSMQRegistry()

Dim ft As FILETIME

Dim strBuffer As String

Dim nBufferSize As Long

Dim nKeyCount As Long

Dim nMaxKeyLength As Long

Dim hKey As Long

Dim hSubKey As Long

Dim strKeyName As String

Dim nDex As Long

Dim strValue As String

Dim strComputerName As String

Dim nReturn As Long

strComputerName = ComputerName

strComputerName = Left(strComputerName, Len(strComputerName) - 1)

strValue = strComputerName & "\private$\Notifications"

If RegOpenKeyEx(HKEY_LOCAL_MACHINE,
"SOFTWARE\Microsoft\MSMQ\Triggers\Data\Triggers", 0, KEY_READ, hKey) =
ERROR_SUCCESS Then

If RegQueryInfoKey(hKey, vbNullString, 0, 0, nKeyCount, nMaxKeyLength, 0, 0,
0, 0, 0, ft) = ERROR_SUCCESS Then

For nDex = 0 To nKeyCount - 1

strBuffer = Space(nMaxKeyLength + 1)

nBufferSize = Len(strBuffer)

RegEnumKeyEx hKey, nDex, strBuffer, nBufferSize, 0, vbNullString, 0, ft

strKeyName = Trim(strBuffer)

If RegOpenKeyEx(HKEY_LOCAL_MACHINE,
"SOFTWARE\Microsoft\MSMQ\Triggers\Data\Triggers\" & strKeyName, 0,
KEY_ALL_ACCESS, hSubKey) = ERROR_SUCCESS Then

nReturn = RegSetValueEx(hSubKey, "Queue", 0, REG_SZ, strValue,
Len(strValue))

End If

Next nDex

End If

End If


End Sub