Archive for the ‘Uncategorized’ Category

Error “Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information”.

October 24, 2014

I was installing a new SSD drive in a desktop computer.

For this i used a USB 3.0 usb-drive (Kingston Datatraveler 100 G3 16 GB ), on which i had put the Windows 7 x64 SP1 installation files, using the Windows 7 USB/DVD tool.

This process had worked for about a hundred previous installations 🙂

It was the first time i used this USB 3 drive for installing Windows 7

And yes,i got the error

Error “Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information”.

Tried Shift-10 and starting diskpart, doing the partitioning myself, but didn’t help.

Cahnged some BIOS settings, but no luck.

Then i saw this post:

http://www.sevenforums.com/installation-setup/333243-setup-unable-create-new-system-partition-new-ssd.html

And yes, after doing the exact same process with a USB 2.0 drive, it worked flawlessly.

Office 2010 activation fails after SP2 with error 0x80070190

August 3, 2013

After installing SP2 for Office 2010, i was unable to activate the office installation. Although i entered the correct key, it wouldn’t activate, throwing the error “0x80070190” office couldn’t be activated.

Turned out that the solution was to start any of the office programs as admin (run as administrator) and then start the activation. Worked flawless then…

Change Max Upload Size WordPress Lighttpd

July 5, 2013

Reminder for self:
edit /etc/php5/cgi/php.ini and set post_max_size = xM to the desired value
restart lighttpd

Deploying Windows 8? Not with ConfigMgr 2007…

September 21, 2012

Windows 8 and SCCM 2007 / 2012
I just read this post from the ConfigMgr team about support for Windows 8 and Server 2012 in ConfigMgr versions.
Although Windows 8 and Server 2012 will be fully supported as ConfigMgr clients for ConfigMgr 2012 SP1 and ConfigMgr 2007 Sp2, the deployment of Windows 8 or Server 2012 through the ConfigMgr Operating System Deployment (OSD) feature will NOT be supported with ConfigMgr 2007 SP2.
So, if you want to a large scale deployment of Windows 8 and/or Server 2012 in your environment, you will have to upgrade your ConfigMgr 2007 environment to ConfigMgr 2012 SP1.
Oh, and with “upgrade”, i mean “replace”.

That’s right, there is no option to in-place-upgrade your ConfigMgr 2007 environment to ConfigMgr 2012.
You can do a side-by-side migration, meaning you install ConfigMgr 2012, migrate all your packages to the new environement, and then migrate your clients.

This is not a problem however,  because ConfigMgr 2012 simply ROCKS!

So, let’s all get those ConfigMgr 2007 environments upgraded to 2012!

Server App-V 2012; error installing Server Application Virtualization PowerShell Cmdlets

April 23, 2012

When installing the Server Application Virtualization PowerShell Cmdlets, i got the following error:

Not very descriptive.
It tells me to look in the installer logfile.
Right,
So, where is that logfile then?
After looking around a bit, I opened the %temp% folder, which on this machine was located in C:\Users\\AppData\Local\Temp, and in there was a folder called “1” with in there… yes logfiles.
In the logfile the following error was shown:

 

Right, now what?
Ah, but wait, there are more logfiles in there:

Great, a clear message.
No problem, i’ll just install .NET FW 3.5 then.

But why wasn’t this mentioned somewhere before? Like, on the “How to install Server App-V Virtualization PowerShell Cmdlets page

File copying in Windows Server 8 beta rocks

April 18, 2012

Just wanted to share some experiences on File Copying in Windows Server 8 Beta.
I was copying two large ISO files to a local VM, but my harddisk didn’t really like this.

So i paused one copy-action, so the other one went faster.  Check this out:

After the first copy-action was done, I resumed the second one:

This looks pretty nice, doesn’t it?

Setting up a Server 8 – System Center 2012 testenvironment… on a laptop – Part 1

April 16, 2012

Working on the road a lot, I wanted to setup a demo/test environment to test Windows Server 8 Beta, together with System Center 2012.
As you might know, you need SP1 for SC2012 in order to properly run on / support Windows Server 8.
Now at this time the SP1 is only in CTP status, so we’ll just have to deal with that.
First get the download for SP1 CTP here.
The download includes 2 updated items of System Center 2012; SCVMM and DPM.
Which means that the other components (SCCM, SCOM, SCSM, Orchestrator, Applocker) are already Windows 8 compliant. Or are they? Let’s find out.

    Building the lab.


So, i’m running a Dell Precision M4600 laptop, equipped with a Core i7 2860QM CPU, 16 GB of RAM, an internal 750 GB SATA harddrive, and an external 1 TB E-Sata harddrive.
This is my one and only system for day-to-day work, so i’m running a triple-boot on it.
First a Windows 7 x64 Enterprise installation, for normal day-to-day operations.
Second, a Windows Server 2008 R2 Enterprise running from VHD, which i use as a Hyper-V host, running a demo environment of SCCM 2007, SCVMM 2008 R2 and SCOM 2007.
And finally, another VHD of 60 GB to which I installed Windows Server 8 Beta.
The VHD disks were easily created from within Windows 7, choosing Action->Create VHD in Disk Management. No need to get diskparty-ing when you can just run this from the GUI, right?
Then after creating these VHD’s, rebooting and starting the Setup of Windows Server, on the bit where you get to select the harddrive to install to, I pressed Shift-F10 to get a command prompt.
Then type diskpart, and mount the VHD file by typing “Select vdisk file=”
Then just type “attach vdisk” and the disk is mounted.
Exit diskpart, and exit the command prompt, to continue with the Windows Server installation.
Now going back to the Windows Server installation screen where you can select the disk/partition to install to, press Refresh, to get the newly mounted vdisk as an option to install to.
Choose the vdisk, and continue the install.
Piece of cake huh? If you need more guidance on this, just do a google/bing query for “Install Server 8 to VHD”.
I had previously did this also for Windows Server 2008 R2 on another laptop, so i only had to re-add this VHD installation to the bootmenu of the laptop . How?
By doing a little bcdedit, to basically create a new copy of the exisiting bootmenu, and adding the path to the VHD to it.
Here’s the tech info for it on teh technetz.
So, now that we’ve got the basics set up (installed Windows Server 8 Beta to VHD), let’s go configure it.
Well, in the next posting then.

SCCM 2012 PXE not working after failed OSD TS

April 8, 2012

When i was doing my first OSD TS with SCCM 2012, the TS failed at first. Of course 🙂

I got a nice error 0x80004005 during a “Build and Capture” sequence, at the point where it was supposed to start installing windows 7 x64 to my VM.

When opening the smsts.log file it told me that i had made a bad combination of Boot image (x86) and the Windows  7 version i wanted to install (x64)

Well that made perfect sense, so i changed the boot image, and was ready to retry the operation.

But hey, after rebooting, i would no longer get a PXE boot.

Nice,

I had advertised the TS to the “All unknown computers” collection, but i suspected that even though this TS had failed pretty fast, somehow a record of the new computer had been made in SCCM.

And when a record has been made for the copmuter, it is of course no longer an “Unknown Computer”.

And yes, in the Collection “All Systems”, there was a new Computer object, called “unknown computer”

Hey, that’s a new one. An Unknown Computer, which is in itself no longer an unknown entity, because there is a record for it in SCCM.

And therefore, it has become a member of the “All Systems” collection, and is no longer a member of the “All Unknown Computers” collection.

Can anyone still follow me? 😛

To make a long story short, just delete this object, update the collection membership, and PXE is working again for the new computer

SCCM – An error occurred while trying to initialize the Windows Deployment Services image server. Error Information: 0xC1030104

February 17, 2012

Got the above error after updating the SCCM boot images with some network drivers.
The PXE service wasn’t running, because the Windows Deployment Service service had stopped.
When starting this service manually, the above error occured
Usually people remove and re-install the PXE Point sccm Role, and/or the WDS Windows role.
What worked for me was just to refresh the boot image packages on the server. Nothing more.
Then the WDS service would start properly, and PXE worked again.
So, if you get this error, first simply try refreshing the packages containing your boot images.

IIS fails after Renewal of SSL certificate – The page cannot be displayed –

February 8, 2012

Scenario: After a PKI infrastructure migration, we were renewing SSL certificates on webservers, to replace all certificates issued by the old CA, by new certificates provided by the new CA.
Problems arose when we bound the new certificate to an IIS instance; the website on which it was used would stop working.
When you typed in the url of the website, you would simply get a message ” The page could not be displayed”
After using the SSL Diagnostics tool it turned out the private key was missing.
Of course, IIS doesn’t complain about that when you assign the certificate to the website… 😦
So, how did the private key turn up missing?
Well, we generated the certificate using the Web Enrollment page of the internal CA server. Then when you click the generated certificate, is is placed automatically in the Personal certificate Store.
We then just cut-paste the certificate to the Computer certificate Store.
But alas, that doesn’t include the private key then! So, you have to manually Export the ssl certificate from the Personal store, including the privaate key, and then import it into the local Computer certificate store.
Only then will it work for IIS.
Thanks to this article for helping us out