|
|
I came across an issue after updating to Windows 8.1 with the keyboard language being set to United States instead of United Kingdom even though UK was set as default.
To resolve the issue I needed to go to the charms menu, click settings, the control panel then click language.
You will probably see (English UK) and (English US) click the US keyboard and click options, click ‘add an input method’ and click UK keyboard, click add.
You will then notice that ENG US appears next to the clock, click on it and change it to UK keyboard, this solved it for me.
At the end of a SBS 2008 to SBS 2011 migration i was attempting to uninstall Exchange 2007 and received the error message.
(Uninstall cannot continue. Database ‘Mailbox Database’ This mailbox database contains one or more mailboxes. To get a list of all mailbox’s in this database run the command Get-Mailbox -Database . To disable a mailbox so that you can delete the mailbox database, run the command Disable-mailbox)
It appeared there were some system mailboxes still in the mail store that couldn’t be removed automatically.
To move the mailboxes use the following commands replacing your mailbox details with these.
1. Open the console the FinalDC in the Start Menu below Microsoft Exchange Server 2010. Once the console is open run this command (I have added the literal names of your databases to this command for you):
Get-Mailbox -Arbitration -Database “Mailbox Database” | New-MoveRequest -TargetDatabase “Mailbox Database 2013010811”
2. Once that is done successfully, you should see the ExchSwingTool confirms that there are no mailboxes remaining on the TempDC Exchange 2007 store.
3. You will need to use Exchange Manangement Console to remove any remaining Move Requests reports or pending requests, then you can decommission the TempDC Exchange.
I did a server migration over the weekend SBS 2003 to SBS 2011 everything went fine except some of the machines would do strange things when it came to moving the users shared folders, I noticed the Desktops would redirect fine but the users My Documents would not update the sync center with the new location or they would have both locations and would appear to be syncing both, like i said very strange things yet some of the machines were absolutely fine.
One of the clues that lead me to believe it was a corrupt csc file was by right clicking on one of the folders that did work eg the My Pictures folder it said it was working offline even though it wasn’t, to repair the csc folder you need to do the following.
Start regedit
1) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters
2) Right click go to new and then DWORDValue
3) Type FormatDatabase and press enter
4) On the Edit menu, click Modify
5) Type 1 in the Value box and click OK
6) Exit regedit
7) Restart the Computer
I received this error (mapiexceptionnetworkerror: unable to make connection to the server (hr=0x80004005, ec=2423)) when attempting a move mailbox request from Exchange 2003 to Exchange 2010 after a little digging it appears both servers need to be able to talk to each other using the short name and the FQDN in my case the Exchange 2010 server couldn’t ping the Exchange 2003 server using the FQDN but it could the short name.
In my case it turn out DNS service had stopped when i restarted it everything worked fine, if this isn’t the case in your situation you could always add an entry into your DNS zone or create an entry in your host file to get around the problem.
When saving an email message to a network drive, I get the following error;
“The message interface has returned an unknown error.”
Instead of saving the message, a tmp-file is created on the network location. When I rename the tmp-file to .msg, then it appears to be the message that I tried to save.
How can I get rid of the error and have the message save directly as an msg-file?
This issue appears to be specific to running Outlook 2007 or Outlook 2010 on Windows Vista or Windows 7. It also appears to happen more often to network shares that are either part of a Distributed File System (DFS) structure or located on storage hardware which isn’t running on Windows like a dedicated NAS system.
The solution is to disable a feature called “Robustified UNC” via the Registry;
Outlook 2007 Key
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options
Outlook 2010 Key
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options
Value name: DisableRobustifiedUNC
Value type: REG_DWORD
Value: 1 turn to 0
While the registry key is located in the Word hive, it actually applies to Outlook (and other Office applications) as well. Due to its location, it could be required to close all open Office applications before changes to take affect (or simply restart your computer).
A Windows 2008 R2 Domain controller started coming up with with the following error, coincidentally at the same time one of the drives failed in the raid array
STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning.
Error Status: 0xc0000001. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.
- Restart the server and press F8 key, select Directory Services restore mode.
- Log in with the local administrator username and password
- Type: cd \windows\system32
- Type: NTDSUTIL
- Type: activate instance NTDS
- Type: files
- If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
- Type: cd\
- Type: md backupad
- Type: cd \windows\ntds
- Type: copy ntds.dit c:\backupad
- Type: cd \windows\system32
- Type: esentutl /g c:\windows\ntds\ntds.dit
- This will perform an integrity check, (the results indicate that the jet database is corrupt)
- Type: esentutl /p c:\windows\ntds\ntds.dit
- Agree with the prompt
- Type: cd \windows\ntds
- Type: move *.log c:\backupad (or just delete the log files)
This should complete the repair. To verify that the repair has worked successfully:
- Type: cd \windows\system32
- Type: ntdsutil
- Type: activate instance ntds
- Type: files (you should no longer get an error when you do this)
- Type: info (file info should now appear correctly)
I then rebooted and windows started normally.
I had an issue last night when a remote server that I was applying windows updates to, hung while it was shutting down. I will still able to ping the server, and access its file shares, but was unable to get RDP access. I was cursing at this point, with the prospect of a long journey the following day to investigate and bring the server back online. I then considered what other steps I could take to try and force the server to reboot remotely. I used the PSTools command psexec to see if I could still get command line access to the remote server, and fortunately I could. Next I tried to force a reboot of the remote server using psexec and the shutdown command as follows, where REMOTE_SERVER_NAME is the name of the remote server that I was trying to reboot:
psexec \\REMOTE_SERVER_NAME shutdown /r /t 01
alternatively you could use:
shutdown /m \\REMOTE_SERVERNAME /r /t 01
This returned the following error:
1115 A system shutdown is in progress
This basically meant that a system shutdown was already in progress, and therefore the command was unable to force a reboot. In the end I used the pskill command to stop the winlogon service on the remote server to try and release whichever process wass causing the server to hang on shutdown. I should stress that this was a last resort, and not something that I would recommend doing unless essential:
pskill \\REMOTE_SERVER_NAME winlogon
Anyway, after another few minutes the remote server did finally restart, although there are a few other things that I should mention that happened in the process. The operating system on this machine was Windows Server 2008 R2. After the server came back up (verified by ping -t REMOTE_SERVER_NAME) I tried to RDP the box again. I was able to enter my credentials and the logon process appeared to start, but after a few seconds the following message appeared on the screen:
Please wait for the Windows Modules Installer
The machine sat like that for quite some time, and then started ‘Configuring Updates’. My RDP session then abruptly ended and the server restarted itself again. Again, when it was back up I tried to RDP the server again and received the ‘Please wait for the windows modules installer message’ for a second time. Thankfully, after a few minutes and another ‘configuring updates’ message, logon continued and ther server was back up and running. On checking the event log and windows update log I was able to verify that all the updates had installed OK, and there were no other errors worthy of note. So in summary, if you want to save yourself a long trip, to most likely press a power or reset switch, you may want to try the above first.
I needed to change the port for outgoing emails on on of our SBS 2003 server to 587 as the new host doesn’t use port 25 for outgoing emails, at first i thought this might be set in the SMTP connector but that is not correct.
The listening port and outbound TCP port are actually located under SMTP protocols in Exchange System manager.
I got all this information from Microsoft KB274842
How to Change the SMTP Listening Port
To change the SMTP listening port on a server that is running Exchange 2000 or Exchange 2003 from port 25 to another port, for example, port 26, follow these steps:
Start the Exchange System Manager.
Locate and click Servername, click Protocols, and then click SMTP.
Right-click the Default SMTP Virtual Server object, and then click Properties.
On the General tab, click the Advanced button, click the Edit button, and then set the Transmission Control Protocol (TCP) port to 26 (or whatever new value you require).
This method sets the port that this virtual server listens to for SMTP traffic.
Warning If you change this port number, the virtual server will not be reachable by other SMTP virtual servers that are configured to have the default (Outgoing) SMTP port 25.
How to Change the Outbound TCP Port
NOTE: Every remote SMTP server that you want to communicate with must be configured to accept connections on the specified port. In most cases, you do not want to change the default port setting.
To change the outbound TCP port, follow these steps:
Start the Exchange System Manager.
Locate and click Servername, click Protocols, and then click SMTP.
Right-click the Default SMTP Virtual Server object, and then click Properties.
Click the Delivery tab, and click the Outbound connections button. Set the TCP port to 26 (or whatever value you require).
Quit the Exchange System Manager for the changes to take place.
All outbound SMTP traffic is now sent to port 26 on other servers.
First select the source and destination locations by clicking the options button and selecting the appropriate options and save this file, i then created a batch file with the follow commands.
“c:\program files\richcopy\richcopy\richcopy.exe” /PF myfile.rcx
This assumes you save the Richcopy options file to the program files directory and on a 32bit machine if using a 64bit machine alter the program files folder to suit.
I came across a Windows 7 machine that kept logging on with a temporary profile, after i removed the profile folder in C:\Users, after a bit of digging it was due to a registry key being wrong, this key is located in.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList in here you will see an entry called S-1-5-21 with the extension .bak i deleted this key and rebooted it then generated a new profile properly.
I have also seen this happen on Windows 2008 Terminal Servers.
|
|
