Where is sysprep in Server 2008 R2
By Jesse | September 3, 2010
You can find the sysprep command in server 2008 (and server 2008 R2) in the c:\windows\system32\sysprep directory. Running sysprep will start the GUI.
DO NOT RUN THE SERVER 2003 VERSION ON SERVER 2008.. You must run the version of sysprep that corresponds the the OS you are cloning.
![[del.icio.us]](/wp-content/plugins/bookmarkify/delicious.ico)
![[Digg]](/wp-content/plugins/bookmarkify/digg.ico)
![[StumbleUpon]](/wp-content/plugins/bookmarkify/stumbleupon.ico)
Topics: Uncategorized | No Comments »
Microsoft.DigitalRightsManagement.Utilities.ADEntrySearchFailedException: Failed to find an entry in the Active Directory: id= ….
By Jesse | July 2, 2010
If you receive this error when trying to get account certificates for either RMS or ADRMS, check your email attribute under the general tab in Active Directory. Not having an email attribute will cause RMS to fail with this error. If you run debug view you will get :
Microsoft.DigitalRightsManagement.Utilities.ADEntrySearchFailedException: Failed to find an entry in the Active Directory:
followed by a sid such as id=s=1-5-20-201919293….. etc…
Populate an email address in this field and you should find you can now sucessfully authenticate and get RAC’s for RMS.
Topics: Uncategorized | No Comments »
FIX for: Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
By Jesse | June 28, 2010
I recently encountered this error with Fedora 13 when trying to run yum:
Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
to fix it, goto /etc/yum.repos.d
and rm packagekit-media.repo
I’m not sure why this file is created but it’s not necessary.. Delete it and the problem goes away.. Yum will start behaving normally again.
Topics: Uncategorized | No Comments »
HOWTO: VMWare 2.0.2 on 2.6.33.5-124.fc13.x86_64 Fedora 13
By Jesse | June 28, 2010
This article describes the process we went through recently to get VMWare Server 2.0.2 to run on the latest kernel in Fedora 13.
You can get VMWare Server to run on Fedora 13 with out too much trouble.
1. Disable SELinux.
Goto Administration –> SELinux Management and set it to disabled. Then Reboot
2. Turn off the Firewall…
If you want you can alternately use a tool like fwbuilder to enable port 902, 8222 and 8333, but in our example for now, we’re just going to turn it off .
3. Now we need the vmmodules that will work with the new kernel.
I got them by using a sneaky trick- They’re in VMWare Workstation which the company keeps much more up-to-date than VMWare Server. If you go download vmware workstation and then install it (the .bundle file is an executable, you need to make it so by running chmod 777 ___________ where _________ is the path to the file+filename.
once you’ve installed vmware workstation the modules are in /usr/lib/vmware/modules/source just copy them to you desktop for now.
4. Now uninstall vmware workstation.
vmware-installer -u vmware-workstation
5. Now you’re ready to install vmware… so install vmware server 2.0.2 now…. It will fail when it tries to run vmware-config.
6. once it finishes, replace the vmware module sources with the ones you saved off above (they’re in the same location you’ll find the vmware 2.0.2 source modules in /usr/lib/vmware/modules/source. Replace these with the ones you saved off from vmware server.
7. Now you need one final tweak… If you try to compile now it still wont sucessfully run vmware-config.
to fix this, open /usr/bin/vmware-config.pl using vi or another editor…
search for :
if (-e $answer . ‘/linux/utsrelease.h’) {
$uts_headers .= “#include <linux/utsrelease.h>\n”;
and replace with:
#if (-e $answer . ‘/linux/utsrelease.h’) {
#$uts_headers .= “#include <linux/utsrelease.h>\n”;
if (-e $answer . ‘/generated/utsrelease.h’) {
$uts_headers .= “#include <./generated/utsrelease.h> \n”;
Finally run vmware-config.pl and it should now compile and install successfully.
Topics: Uncategorized | No Comments »
Fix for: Exchange – In maintenance mode status
By Jesse | May 21, 2010
If one of your servers is listed as “In maintenance mode” under status in exchange system manager, it is easy to fix.
The error looks like this:
This is an example of exchange, with a server in maintenance mode.
To fix this, in this window, right click on the server, goto properties, and uncheck “disable all monitoring of this server.”
Then wait a while, it takes about 5 minutes for the status to change to Available.
Topics: Uncategorized | No Comments »
Fix for: Outlook 2003 can’t connect to Exchange 2010
By Jesse | May 19, 2010
If you try to connect an Outlook 2003 client to an exchange 2010 server and you find it doesnt work, try this first, this will fix it.
In Exchange 2010, they have enabled “Encrypt data between outlook and exchange”. This was not enabled in prior versions of outlook. If you go into properties of your exchange connection, it’s listed under the security tab at the top. Just check the box, completely close outlook.. Reopen it and it should now connect.
If you want a walkthrough please see below:
- Goto control panel and open the mail icon. From the mail icon, you will see the screen below. Select Email Accounts:
- Select View or change existing e-mail accounts, then next:
- Select your Microsoft Exchange Server connection then press “Change”:
- Select “More Settings…”
- Select the security tab and the enable “Encrypt data between Microsoft Office Outlook and Microsoft Exchange server.”
- Close and restart outlook and you should now be able to connect to Exchange 2010 from Microsoft Outlook 2003.
Topics: Uncategorized | No Comments »
BHCBlog linked to on Technet!
By Jesse | October 27, 2009
http://social.technet.microsoft.com/Forums/de-DE/windows_Serverde/thread/f83dd416-6d58-4bb8-84f8-4d2f92c213e1
Neat!! I’m the top link on a Microsoft TechNET article.!! Very cool!! Now if only I spoke German!
Topics: Uncategorized | No Comments »
FIX for : Configuration Manager: The Specified device instance handle does not correspond to a present device
By Jesse | October 17, 2009
We have encountered this issue several times…. the fix for this is to open regedit and browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\.
If there is an enum key here, rename it to old_renum
this should fix this issue related to Configuration Manager: The Specified device instance handle does not correspond to a present device.
Questions, comments or suggestions welcome.
Topics: How To | 5 Comments »
SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security. Event ID 17806
By Jesse | October 8, 2009
This article is solved in a previous post.
Basically this error is sometimes seen when you are trying to access sql from the SQL server either via ODBC or via an application such as during the installation or RMS (Rights Management Services) . To resolve this issue you can add the DisableLoopbackCheck registry entry.
this will fix the three errors you may see in Event Viewer on the SQL server. These errors are:
Failure Audit :: Login failed for user ‘<DOMAIN>\<USERNAME>’. (CLIENT x.x.x.x) where domain and username are the ones supplied to access SQL.
Error :: SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security; the connection has been closed (CLIENT: x.x.x.x) — Event ID 17806
Failure Audit :: Login failed for user “. The user is not associated with a trusted SQL Server connection.
To see the full resolution of this issue please follow this link.
Topics: Uncategorized | 1 Comment »
Fix for Login failed for user “. The user is not associated with a trusted SQL Server Connection.
By Jesse | October 8, 2009
This article provides a fix for the error:
Login failed for user “. The user is not associated with a trusted SQL Server Connection. (CLIENT: 127.0.0.1)
This error has several causes- one of which is an application or ODBC connection that is initiated from the same machine as the SQL server (ie the server is connecting to itself). The easiest fix for this is to temporarily or permanently disable the loopback check ….
- Edit the registry using regedit. (start –> run … Regedit <Enter>)
- Browse to : HKLM\System\CurrentControlSet\Control\LSA
- Add a DWORD value called “DisableLoopbackCheck”
- Set this value to 1
You should now find that the connection will complete successfully. Another place to check is in event viewer. For this particular error we had 3 events logged in event viewer:
1. Failure Audit :: Login Failed for user ‘<DOMAIN>\<USERNAME>’. (CLIENT 127.0.0.1)
2. Error :: SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security; the connection has been closed. (CLIENT 127.0.0.1)
3. Failure Audit :: Login Failed for user “. (CLIENT 127.0.0.1)
The above steps resolve this issue.
Below is an article that discusses in more detail disabling the loopback check.
http://support.microsoft.com/kb/896861
Topics: Uncategorized | 2 Comments »
« Previous Entries