weberj.ch

Hi

I’m wondering who is reading my old stuff… because I’ve received many comments! – But honestly maybe some bots are creating some nice comments today, because I never thought that somebody will read trough that stuff. What a nice and optimistic idea of the usage from bots :-p

After one year taking off ( no new posts), I’m consindering about building a new Website.

Sorry for my English… but you have to know there were times when it was worse.

Der Windows Gerätemanager ist eines der wichtigsten Programme im Umgang mit Hardware und deren Treibern. Jedoch gibts da ein Problem…nicht alles wird automatisch angezeigt. Doch wie meists existiert einen Trick

1) Open the “Start” menu and choose “Run…”
2) Type in “cmd” (without the quotes) and click “ok”.
3) At the cmd prompt, type in “set devmgr_show_nonpresent_devices=1″ (without the quotes) and press enter. (Note that nothing seems to happen–this is ok. We are actually setting an environment variable which is going to help us to see hidden devices)
4) On the next cmd prompt line, type in “devmgmt.msc” (without the quotes) and press enter. This will launch the Windows Device Manager Console.
5) In the Device Manager Console, from the “View” menu, select “Show Hidden Devices”.

gefunden auf: http://www.tech-recipes.com

http://www.hirensbootcd.net/download.html

Immer gut zu gebrauchen…z.B. wenn das BIOS ein PW gesetzt hat..

StartupItems welche unter /Library/StartupItems/ liegen müssen umbedingt die richtigen Rechte besitzen!
Diese sind wie folgt fest zu legen:
sudo chown -Rh 0:0 .
sudo chmod -R go-w .

-> Beispiel: StartupObjekt von WireShark, welches die Rechte für die NW infraces vergibt

If you are trying to install multiple software packages using a ConfigMgr task sequence “Install Software” step, where each of the package and program combinations is stored in a task sequence variable (e.g. PACKAGES001=XXX00001:Install), you might find that they don’t work. If you go digging through the SMSTS.LOG, you’ll see messages like this:

No matching policy assignments received.
Policy download failed, hr=0×80004005

This is because you have to give ConfigMgr permission to install a package that isn’t advertised to the computer. (ConfigMgr always tries to be “secure by default” and making this the default would violate that principle.) This is done using the “Allow this program to be installed from the Install Software task sequence without being advertised” checkbox on each program’s properties. The explanation given in the ConfigMgr documentation (http://technet.microsoft.com/en-us/library/bb680842.aspx) is:

Important

The program specified must have the Allow this program to be installed from a list of software packages in the “Install Software” task sequence step without being advertised option selected or the installation will fail. This option can be selected when adding a program to an existing package in the New Program Wizard. Alternatively, you can specify this option by right-clicking an existing program, selecting clicking Properties, and then clicking the Advanced tab.

Copyright by: http://blogs.technet.com/b/mniehaus

Edit:
Bei mir lags an den Zugriffsrechten, welche in der LAB Site anders gesetzt waren als in der PROD…
Lösung des Fehlers: Package /Program/ Start in: ungebedingt leer lassen!

[ConfigMgr] KB 961105 – Error message when you try to import OSD drivers in System Center Configuration Manager 2007 Service Pack 1 systems: “The selected driver is not applicable to any supported platforms”

The Import New Driver Wizard completed with errors. For more Information about the tasks that were not completed, see details.

In the details section, you see the following information:

Error: Some driver(s) can not be imported successfully. Please see following details.
Error: Failed to import the following drivers: – The selected driver is not applicable to any supported platforms.

This problem occurs if the driver .inf file only has information for Windows Vista and has no information for any other operating system, such as Windows Vista RTM.

http://support.microsoft.com/default.aspx?scid=kb;en-us;961105

copyright by: http://wmug.co.uk/blogs/cliffs_blog/

Abhilfe schafft eine veränderung des .Inf File Parameters [Manufacturer] zB.
von
::[Manufacturer]
::%Company% = HP,NTx86,NTamd64zu
von
[Manufacturer]
%Company% = HP, NTx86.6.1.1
…

Task Sequence: has failed with the error code (0×80091007). The full error is “the hash value is not correct”.

Workaround:
One common solution is to change the advertisment to access content directly from a distribution point when needed by the running task sequence, but that’s really not needed…

Instead, most times it’s the Settings Package that is failing and you only need to Update the Distribution Point for that package and then everyhing works just fine…

copyright by: http://www.deployvista.com/

First we need to convert this hex based error message to decimal. In order to do this we can actually use the good old SET command.
To convert hex 0×80070652 we use the last 4 numbers and type this command:
set /a c = 0×652

This command will give the output 1618. In order to read the error message we simply type:
Net helpmsg 1618

This will give us this output that explains the reason for the error message:
Another installation is already in progress. Complete that installation before p
roceeding with this install.

Copyright by : http://www.moe.am/

function CheckSnapin($snapinname)
{
	if(!(Get-PSSnapin |
		Where-Object {$_.nname -eq $snapinname}))
	{
		if(!(Get-PSSnapin -registered |
			Where-Object {$_.name -eq $snapinname}))
			{
			"$snapinname is not registred. Exit script."
			exit
		} #end if registered
		ELSE
		{
			add-pssnapin -name $snapinname
		}	#end else registred
	} #end if not get-pssnapin
	ELSE
		{ "$snapinname cmdlets allready loaded"}
	} #end CheckSnapin

CheckSnapin("Quest.ActiveRoles.ADManagement")

http://blogs.technet.com/b/heyscriptingguy/archive/2010/06/16/hey-scripting-guy-how-can-i-sign-windows-powershell-scripts-with-an-enterprise-windows-pki-part-1-of-2.aspx
http://blogs.technet.com/b/heyscriptingguy/archive/2010/06/17/hey-scripting-guy-how-can-i-sign-windows-powershell-scripts-with-an-enterprise-windows-pki-part-2-of-2.aspx

$cert=(dir cert:currentuser\my\ -CodeSigningCert)
 Set-AuthenticodeSignature? *Script* $cert -TimeStampServer http://timestamp.comodoca.com/authenticode