Updates from October, 2009

  • Windows 7 on an IdeaPad S10e

    Mirco 19:01 on Monday, 26. October 2009 | View Comments Permalink | Reply
    Tags: , diskpart, driver, ideapad, , lenovo, , netbook, s10e, upgrade, , win7, , windows7

    Last week Microsoft introduced the new Windows 7 to the humble consumer and since I’ve known about the increased performance over Windows Vista from the Beta program it was to to send the installation of Windows XP on my netbook into retirement for good.

    The Atom processor of the S10e doesn’t support 64 Bit operating systems and the onboard graphic isn’t the fastest either. And since I rarely store any data directly on the netbook I won’t need the BitLocker feature, so I went for a solid 32 Bit Home Premium version. These are available as System Builder Version from 69€ to 89€ at retail shops (perfectly legal according to German law). The only differences to the regular retail version is the missing 64 Bit DVD and the lack of Microsoft support.

    The first obstacle was the DVD. The IdeaPad, like any netbook, doesn’t have an internal optical drive. So I have two options:

    1. use an external USB DVD drive
    2. copy the DVD onto a USB thumb drive (at least a 4GB size)

    I went with option 2 because I didn’t want to buy a new DVD drive.

    Before I started to copy I had to prepare the thumb drive using some command. Open the Command Prompt (CMD) as an Administrator (important!).

    c:>diskpart
    DISKPART>lis dis
    DISKPART>sel dis 3 (3 was my thumb drive)
    DISKPART>lis par
    DISKPART>sel par 1 (1 usually the only partition on the thumb drive)
    DISKPART>format fs=FAT32 LABEL=”Windows 7” QUICK OVERRIDE
    DISKPART>active
    DISKPART>exit

    Your thumb drive should now be empty and most importantly bootable.

    Now insert the Windows 7 DVD into your DVD drive (D:) on your PC and copy the content to the thumb drive (G:) using Robocopy. (use drive letters that match your configuration)

    c:>Robocopy d: g: *.* /e /copyall

    This could take a while, depending on the writing speed of your thumb drive. Now you can boot the netbook with the memory stick and start the installation process. I still had the original recovery partition which I wanted to keep. I had to choose custom setup to select the system partition for installation. The automatic mode went into a menu loop because the recovery partition (the first partition on the disk) was too small to install Windows 7. A simple error or warning message would have helped at this point.

    The main installation was done within 30 minutes.

    From good tradition the first thing I did was to run Windows Update. It found only 9 updates, most of which where device drivers. but still I missed some functionality.

    • Microphone
    • Bluetooth
    • Energiemanagement
    • Multi Touch function of the touchpad

    Lenovo doesn’t provide any Windows 7 drivers to the IdeaPad S10e, since the device is currently phasing out and is only sold with Windows XP. But the new IdeaPad S10-2 is sold with Windows 7 and besides some minor differences it’s practically the same hardware.

    Here’s a list of needed device drivers:

    For the 3G version of the S10e you’ll need additional UMTS card drivers. There’s a complete list of all working drivers and tools at the ThinkPad Forum (only German content, but the drivers are available in Englisch).

    Update: I just found a video tutorial

    Click here for Part 2

     
  • SCOM Agent Trouble

    Mirco 13:16 on Thursday, 28. August 2008 | View Comments Permalink | Reply
    Tags: -2130771964, , console, , , install, , msi, , restart, , , solution, , troubleshooting, uninstall

    Two weeks ago I installed the KB954049 on our Operations Manager servers. This “allows” me to update all of our 1500 agents, that are currently deployed.

    Four days, some Alerts form the IDS and multiple retries later there are still 60 agents left and refusing every attempt to be updated to version 6.0.6278.32. I’m still not sure why a domain administrator gets an “Access Denied” when trying to initiate a remote installation but I will figure this out, eventually.

    Today I noticed something new. Several, already updated Agents are grayed out on the status view. The servers are up an running, according to ping. A short look at the Computer Management shows the Agent is running too, but when I try to restart the service I’m prompted with some error message and the ID: -2130771964.

    Unfortunately Google isn’t a great help finding this error. There are only a handful results that focus on installing agents, but I have trouble restarting the service.

    My next thought was to try the Change/Repair option in “Add/Remove Software”, which stopped with the same Error code as restarting the service. Somebody must have been very creative in defining error codes for these agents.

    OK, if I can’t repair it, maybe I can uninstall it… and it worked, with the slight limitation that the uninstaller was unable to remove the installation folder.

    The next step was redistributing the Agent from the OpsMgr console, which went through with no errors at all.

     
  • Getting the 100 biggest Agent Queues out of your Operations Manager Database

    Mirco 16:00 on Tuesday, 22. July 2008 | View Comments Permalink | Reply
    Tags: , , center, database, datawarehouse, , , , , , query, queue, , , , systemcenter, usage

    Getting a decent overview of you Operations Manager Agents sometimes is a bit hard. There’s a nice graph to display the “Send Queue % Usage” but you have to click through every agent status to find the interesting ones. Most likely the ones with a high percentage status.

    Another way, although with less current data would be to query your Data Warehouse with the following statement

    SELECT     TOP (100) vManagedEntity.Path,
                         vPerformanceRule.CounterName,
                         Perf.vPerfHourly.DateTime,
                         Perf.vPerfHourly.AverageValue AS Avg,
                         Perf.vPerfHourly.MinValue AS Min,
                         Perf.vPerfHourly.MaxValue AS Max
    FROM       Perf.vPerfHourly
    INNER JOIN vManagedEntity ON Perf.vPerfHourly.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId
    INNER JOIN vPerformanceRuleInstance ON Perf.vPerfHourly.PerformanceRuleInstanceRowId = vPerformanceRuleInstance.PerformanceRuleInstanceRowId
    INNER JOIN vPerformanceRule ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
    WHERE      (vPerformanceRule.CounterName LIKE N'%send queue % used')
    ORDER BY   Perf.vPerfHourly.DateTime DESC,
               Avg DESC

    This query returns the 100 Queue with the highest fill rate. Note, that data in the Data Warehouse DB can be several hours behind the Operations Database.

     
  • How to restore a Domain Controller you cannot logon to

    Mirco 6:54 on Wednesday, 16. July 2008 | View Comments Permalink | Reply
    Tags: account, active, active directory, adsi, controller, dc, dcpromo, directory, , edit, kerberos, login, logon, , ntdsutil, registry, restore,

    For some reason we had multiple Domain Controllers that refused any logon attempt in the last few weeks.

    After getting a closer look at the event logs we found pages full of Kerberos errors. Somehow the machine account expired and wasn’t renewed, so the controller could no longer replicate and thou refused our logon attempts.

    I tried to fix the Kerberos issue, but nothing I found was helping the situation. But how do I restore a Domain Controller I cannot logon to, without reinstalling the server?

    After a quick search I found this: Microsoft Article KB332199, which had a useful subsection on the “If the domain controller cannot start in normal mode” issue.

    First restart the Domain Controller in Directory Services Restore Mode (using F8) and open REGEDIT. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions and Edit the value of ProductType from “NavmanNT” to “ServerNT”. Be careful to spell this correctly! This will tell the server that it is only a member server in the domain, and you can use a local logon account.

    Restart the system and logon using the Administrator account with the restore password. Open REGEDIT again and this time browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters. Find the Src Root Domain Srv Entry and delete it. This way the server will believe it’s the last Domain Controller in the current domain.

    Start DCPROMO and create a new temporary domain. Yes, create. No need to delete anything yet. This will overwrite any Active Directory values stored on your local server. After it’s done restart and run DCPROMO again. This time we will shut down the temporary domain and remove all Domain Controller traces from the harddrive.

    That’s it. All you need to do now is remove the Active Directory objects related to the original Domain Controller (KB216498) from the directory, wait for the replication to finish and run DCPROMO to add this server as Domain Controller of your domain.

     
  • The Now! habit in IT

    Mirco 18:58 on Wednesday, 7. May 2008 | View Comments Permalink | Reply
    Tags: , communication server 2007, communicator, , habit, , , , now!, ocs, , planning

    Yesterday, 15:30 at the office of my current customer.

    IM: “Could install the Communication Server today?”

    What?

    OK, we had made the required preparations on the Active Directory, but haven’t done any planing on how or where to place the servers. All I knew for certain at this point was that we had to install the enterprise version of Office Communication Server 2007 due to the amount of users.

    So we ended up with four people installing the server on a virtual machine. After we ran the Schema, Forest and Domain prep tools we started installing the server, the database on a separate machine and started the service.

    Everything seemed OK so far.

    When we tried to test a client we could log on. The Eventlog indicated that the server name couldn’t be resolved by the DNS.

    That’s why I love proper planning.

    I remembered we had to add some SRV records to the DNS. So we looked through the installation manual and added some _sipinternaltls _tcp SRV records to each domain in the forest.

    Next problem: The certificate could not be verified.

    We couldn’t find any problem with the certificate, and tried some different options in the creation wizard. But still couldn’t log on.

    After checking through all the logs on the client and the servers, we came to the conclusion this had to be a database problem, and since it already was 21:00 we called it quits for the day.

    Today:

    According to the error on the database server the service use of the OCS couldn’t perform write operations, but it had all the necessary permissions. After searching he net we found a KB article on the Microsoft website indicating we should install a patch, available through the support hotline (there wasn’t even a download on the premiere support site).

    Well the patch worked fine on the OCS but failed on the SQL server, because it had more than one database instance.

    So we moved the database to another server with a single instance.

    And it finally worked… after 24h.

    All of this trouble because management all of a sudden decided it had to start mass rollout of the Office Communicator next week.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel