when you install group chat server,file transfer feature is not working.
Group chat server has few services,channel service,lookup service and compliance service.
this problem is related to channel service.Channel service provides a connection between group chat,IIS and SQL db.When client sends a file to chat room,client queries the web site https://fqdn.domain.com/mgcwebservice/mgcwebservice.asmx and access to \\fqdn\gccshare location.I think this folder must be accessible from gcchannel user and everyone.
follow these steps for IIS 7
1.remember the gcchannel service account password :)
2.if they required ,change service account from "Group Chat Server Configuration tool".sometimes service cant be restarted.check the service logon credential.
3.go to IIS 7 console,in application pool,you will see "MGCWebService application pool".
4.right click to app pool and change the identity credential.
5.in default web site,go to MGCwebservice -IIS section-Authentication
6.7.right click anonymous auth and set "application pool identity"
7.now you can send file to chat room.
ps:check whether your server certificate is correct.you can use a test htm file and hit this link from client and see certificate is true or not.
OCS Group Chat File Transfer Issue
how to move MSDTC resource to different cluster group
as best practice MSDTC resource can be located to different cluster group.
but it s tricky.
MSDTC -install command install MSDTC service
MSDTC -uninstall makes opposite.
msdtc -resetlog
to uninstall msdtc
msdtc -uninstall and then delete these registry keys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
if exists HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC.
--sometimes you see error 4394
--MS DTC's log information has not been configured correctly in the shared cluster ----registry.
--You have to check DCOMCNFG.exe and computer--properties MSDTC tab and log path.
after you uuninstall msdtc service.
reboot and msdtc -install
if you have clustered environment you will see msdtc resource in default cluster group.
to change MSDTC resource to different group ,follow these steps
ps:MSDTC resource group has dependency to disk and Network name.I assume you have another cluster group ,network name and disk resource in it.
1. Offline the MSDTC resource.
a. If moving the resource to a different group The MSDTC resource must be
deleted and recreated
2. Copy the DTC folder from the original drive to the destination drive (c:\windows\system32\msdtc)
3. Open the regedit on browse to "HKLM\Cluster\Resources\MSDTC Resource
GUID\GUID\DtcLogPath" change the value to the new path
4. Change dependency to the New Disk (in different group)
5. From a Cmd line "MSDTC -resetlog"
6. Bring MSDTC resource online
when upgrading OCS R1 to OCS R2
Upgrade list for OCS R1 --> OCS R2
1.download OCS 2007 Global Settings Migration Tool
2.setup MigrateOCS.msi.
3.cscript MigrateOcsGlobalSettings.vbs /Action:MigrateGlobalSettingsTree command.This command will copy the RTC service container to Configuration partition.
4.cscript MigrateOcsGlobalSettings.vbs /Action:MigrateGlobalSettingsProperties
Copy the attributes by using this command.
5.You need to give required permission to new container.
lcscmd /forest /action:ForestPrep /global:configuration
lcscmd/domain /action:DomainPrep
now,wait for replication.This is very important.If you cant replicate the changes to other global catalog servers.You will get "contraint violation" error in next step.
this sets up the permission on new objects.
6.cscript MigrateOcsGlobalSettings.vbs /Action: MigrateServerDnReferences
you are saying to servers ,this is my new configuration container.
/SearchBaseDN:
7.cscript MigrateOcsGlobalSettings.vbs /Action: MigrateUserDnReferences /SearchBaseDN:
you are doing samething to user objects.
8.try to start all ocs services.Then test IM,conference,call features.
If all tests are successfull ,you can run this command:
cscript MigrateOcsGlobalSettings.vbs /Action: DeleteSystemGlobalSettingsTree
SCVMM and ESX integration issue.
as you know,SCVMM 2008 can work together esx server.You can add esx host server to scvmm management konsole and easily manage.top issues about scvmm and esx integration
limited connectivity and security.
When you add esx host to console ,you see OK(limited).this means you cannot perform basic operations like "save state".
to enable Full management over ESX,
go to ESX host-properties security in scvmm console.
you will see credentials for this host and certificate.
enter esx credentials username,password.
Click retrieve and click "accept both the certificate and public key for this host".
now, you can perform lots of operations but you cannot transfer iso and vm template file to esx.
on esx server login on console and
go to /etc/ssh path.
vi sshd_config
click i for insert
find "PermitLoginforRoot no" and change it to "yes".
to exit use ZZ or :wq command.
restart sshd service by using "/etc/init.d/sshd restart"
now enjoy full integrated esx and SCVMM console.
WMI scripts-rename multiple files in a folder
This script can rename multiple files in a specific folder.
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
'You connect to default namespace with moniker method(winmgmt)
Set colFileList = objWMIService.ExecQuery _
("ASSOCIATORS OF {Win32_Directory.Name='C:\Logs'} Where " _
& "ResultClass = CIM_DataFile")
'it seems little different.It connects two wmi class in one command.uses Win32_Directory class for retrieving folder ,uses CIM_Datafile for files.Associators of usage connects two class like joining two db table.
For Each objFile In colFileList
strNewName = objFile.Drive & objFile.Path & "ABC-" & _
objFile.FileName & "." & objFile.Extension
errResult = objFile.Rename(strNewName)
Next
'this is very simple you assign new file name to strNewName variable.You can add prefix or suffix in here.
mpio windows core
· As we all know we have only Windows 2008 core installation provides only command
prompt interface. We have to use commands to configure MPIO. First we have to
enable “Multipath I/O” feature and there use MPClaim to clam all applicable
Multipath device. Following are the steps needed for configuring MPIO
o On Core execute “ocsetup MultipathIo /norestart”
o Restart the server
Execute mpclaim -r -i -a “” after reboot. This will reboot the system
automatically. Once the server is back, MPIO will be configured on the server.