How To Fix ERROR_NOT_FOUND 0x80070490 During Windows 7 SP1 Installation

fonte: http://beerpla.net/2011/05/06/how-to-fix-error_not_found-0x80070490-during-windows-7-sp1-installation/

imageWell, this one took ages. And whenever something takes me ages, rather than write it down in my personal notes, I prefer to put it out online for everyone with the same problem to easily find and benefit from.

The problem I’m talking about today is trying to upgrade your Windows 7 installation to SP1 by applying Microsoft’s update KB976932, called “Windows 7 Service Pack 1 for x64-based Systems” and getting nothing but a failure every time. The same problem may affect 32-bit systems as well, and I’m not sure what the update number for that would be, but the solution should work for either one.

SNAGHTML3837080

The update starts just fine, chugs along for 10 minutes or so, then reboots the system and starts performing more operations, when suddenly one of them fails about 10% down the road, reboots, and reverts the whole process. You end up with this message (code 80070490) and a failure for which there are a lot of useless “solutions” on the web that just don’t work.

Except for one. I can’t take credit for it – all I did was spend a month weeding through the crap, retrying, and getting nowhere, until a genius by the name Ben-IS came up with exactly the right diagnosis and provided exactly the right solution. This solution, in my own interpretation, is below.

Step 1

We are going to use a utility called SFC (System File Checker or Windows Resource Checker), which is part of the Windows installation. It will help diagnose the problem.

Open up a command prompt (cmd) as administrator and run

sfc /scannow

This will run for a while and produce a file called CBS.log which you can find in %WINDIR%\Logs\CBS (usually C:\Windows\Logs\CBS). See this KB929833 for more info on SFC and CBS (Component Based Servicing).

sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Even though there are no integrity violations, we should have enough info in the log to diagnose the problem.

Step 2

Unfortunately, Windows overwrote my CBS.log, so I’ll go by the one Ben-IS provided.

Open up CBS.log and look for something like Failed uninstalling driver updates or0x80070490 – ERROR_NOT_FOUND.

If you have this line, which you should if you’re reading this post, you should also see lines similar to these a few lines above:

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: usbvideo.inf, Ranking: 2, Device-Install: 0, Key: 598, Identity: usbvideo.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16543, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: sffdisk.inf, Ranking: 2, Device-Install: 0, Key: 599, Identity: sffdisk.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16438, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: sdbus.inf, Ranking: 2, Device-Install: 0, Key: 600, Identity: sdbus.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16438, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

One of these .inf files is the culprit, and we’re going to find out which one in the next step.

Step 3

Now open up a different log file located at %WINDIR%\inf\setupapi.dev.log (normally c:\Windows\inf\setupapi.dev.log).

Look for a line that contains Failed to find driver update or FAILURE(0x00000490).

Note the exact path to the .inf file that failed. In my case, it was:

sto: Failed to find driver update ‘C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo.inf‘ in Driver Store. Error = 0x00000490

Step 4

This is the key to the whole operation. Open up the command prompt again (cmd) as administrator and run

pnputil -a INSERT_FILE_NAME_FROM_STEP_3

For example, I ran

pnputil -a C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo.inf

You should see the following dialog:

SNAGHTML3a03ec7

Choose Install this driver software anyway.

The end result should be something like this:

pnputil -a C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo.inf
Microsoft PnP Utility

Processing inf :            usbvideo.inf
Driver package added successfully.
Published name :            oem69.inf

Total attempted:              1
Number successfully imported: 1

Repeat this step for any failures found in step 3.

Step 5

Apply the SP1 Windows Update again – it should now install successfully.

And voila – enjoy your SP1!

Microsoft has failed to fix this incredibly cryptic problem, leaving it up to the users to figure out why their SP1 updates are not installing. Thanks to people like Ben-IS, solutions no longer involve head-banging, postal rage, and f7u12.

Configurare Intel vPro per la gestione remota

fonte: http://www.windowserver.it/Articoli/Networking/ConfigurareIntelvProperlaGestioneRemota.aspx

Autore: Andrea Garattini – Data Pubblicazione: 26 Febbraio 2015

Introduzione
Negli ultimi tempi sono usciti sul mercato alcuni modelli di server low cost molto interessanti: CPU XEON, 32GB RAM, 4 dischi ecc. Sfortunatamente… non hanno funzionalità di gestione remota tipo ILO o DRAC, giusto per fare due nomi.

Questo non è completamente vero, anzi! Tutti i sistemi con tecnologia Intel vPro (quindi anche i client) possono sfruttare la tecnologia Intel MEB (Management Engine BIOS). In pratica, all’interno del chip è stato integrato un server VNC, consentendo molte delle operazioni ottenibili attraverso i classici sistemi Out of Band: Console remota Out of Band, Reboot remoto, Power on e off remoti, Image mounting.

In questo articolo andiamo a vedere come attivare tutte le funzioni di Remote Management per il Dell T20 (ma come detto… vale per qualsiasi sistema!). Il tutto a costo ZERO!

Attivare il MEB

La prima operazione consiste nell’attivazione del MEB. Per farlo è necessario premere CTRL+P all’avvio, figura 1, proprio appena compare lo splash screen (compare in alto a destra la scritta gialla preparing MEBX Menu)

NB: in questa fase non è possibile usare KVM over Network!


Figura 1 – Main Menu MEB

La prima cosa da fare è il login; scegliamo quindi MEBx Login, inseriamo la password di default (admin) e la cambiamo immediatamente con qualcosa lungo almeno 8 caratteri, con almeno un carattere minuscolo, un carattere maiuscolo, un numero e un carattere speciale. Questo è necessario dato che in seguito la password che utilizzeremo per l’accesso in console remota dovrà essere esattamente di otto cifre e con le stesse caratteristiche… tanto vale impostarle uguali!

Dopo l’inserimento della nuova password siamo nel menù del MEB, dove dobbiamo configurare i parametri di accesso remoto.

La prima voce del menù principale, Intel ® ME General Settings – figura 2, consente esclusivamente di cambiare la password di accesso (Change ME Password). La seconda, Intel ® AMT Configuration, figura 3, è invece quella che ci interessa!


Figura 2 – General Settings


Figura 3 – AMT Configuration

Intel ME Network Name Settings – figura 4) e impostiamo Host  Name, Domain Name, dedichiamo il FQDN al solo MEB (Dedicated FQDN) e lasciamo disabilitato il Dynamic DNS Update (è molto meglio configurarla a mano nel DNS).


Figura 4 – Network Name Settings

Torniamo indietro e scegliamo la seconda voce (TCP/IP Settings) quindi Wired LAN IPV4 Configuration. Disabilitiamo il DHCP e andiamo a inserire i valori corretti nei diversi campi. Torniamo alla videata della AMT Configuration e scegliamo la voce Activate Network Access confermando poi al pop-up.

Ok! La parte “BIOS” è terminata… avviamo tranquillamente la macchina e proseguiamo la configurazione.

MEB Tools

Il prossimo passo prevede due strategie: una a pagamento ed una gratuita.

La prima consiste nel procurarsi il VNC Viewer Plus (http://www.realvnc.com/products/viewerplus/index.html), una versione evoluta del solito VNC che contiene al suo interno tutti i componenti necessari per la gestione del MBE (essendo in pratica sviluppato in partnership con Intel proprio a questo scopo).

Se invece vogliamo proseguire a costo zero, dobbiamo scaricare ed installare i tool di Open Manageability dell’Open Software Projects (http://opentools.homeip.net/open-manageability).

Dopo averli installati (su una macchina diversa da quella da amministrare!) lanciamo il Manageability Commander Tool ME. Con il bottone Add Known Coputer  aggiungiamo l’indirizzo IP assegnato in precedenza nelle opzioni MEB, figura 5.


Figura 5 – Nuovo Device da Gestire

A questo punto possiamo selezionarlo dal menù network e con il pulsante Connect ci connettiamo. Se la connessione ha successo il pulsante cambia scritta in Discconnect ma soprattutto di fianco al sistema compare il simbolo di un menù espandibile.

Posizionandoci sopra ed espandendo le voci la prima sorpresa comoda che abbiamo è la lista delle componenti hardware dei sistema, figura 6.


Figura 6 – Elenco Hardware

Andiamo nel tab Remote Control, quindi nell’area Remote Desktop selezioniamo la freccia a destra del Disable in corrispondenza della voce Remote Desktop Settings. Nel menù che compare, figura 7, modifichiamo i valori di State, Standard Port, Redirection Portin Enabled e Local User Consent in Disabled e dopo aver impostato la password (8 caratteri, una maiuscola, una minuscola, un numero e un carattere  speciale) confermiamo con OK.


Figura 7 – Personalizzazione Valori

Lanciamo VNC e… buon management!

NB: sulla macchina “controllata”, per segnalare che un amministratore ha preso il controllo compare una cornice giallo/rossa sul monitor!

NB: almeno sui Dell T20… il gioco funziona se sente un monitor connesso. Spento o acceso non fa differenza. Basta anche solo un KVM, ma vuole qualcosa connesso alla porta monitor.

Windows XP client and Windows server 2012 R2

fonte: http://northtech.co/microsoft/windows-xp-client-and-windows-server-2012-r2/

If you are still running a combination of Windows XP and Windows 7 client machines you may come across an issue when introducing your first Windows 2012 R2 Domain Controller server into your environment that your Windows XP clients no longer run login scripts.  The problem is to do with the versions of SMB which is supported between client and server communication which can cause issues with connecting to shares via UNC or executing login scripts on the DC.

The following image will give you an idea of the versions of SMB between different clients and server.

smb

As you can see Windows XP will only communicate using SMB 1.  Now lets look at the “Server” service property settings of a Windows 2012 (non R2)

smb1-2

You can see that SMB1 and 2 driver is allowed. Now let’s have a look at the “Server” service property settings of a Windows 2012 R2 server.

smb5 (2)

You can see that the server is only allowing SMB 2 and not 1 and this is why you will get issues mentioned above.  There is a workaround until you can upgrade your Windows XP clients and that is to amend the following registry key:-

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerDependOnService

This is how it is by default

smb_1and we need to amend to

smb_2

Once amended reboot the server and if you then check the “Server” service property settings again you will see that it’s changed

smb1-2

Your Windows XP clients will now be able to UNC and successfully run login scripts.  You will need to do this on any additional Windows 2012 R2 Domain Controllers until you have removed these old clients.

I would recommend replacing these legacy clients as it is now end of life and Microsoft will no longer be providing security updates and hotfixes.

Link Aggregate Group (LAG) Configuration on 200/300 Series Managed Switches

fonte: http://sbkb.cisco.com/CiscoSB/GetArticle.aspx?docid=caae365b755f46f5989177cb68216304_Link_Aggregation_on_Cisco_Series_Managed_Switches.xml&pid=2&converted=0

Article ID: 97

Link Aggregate Group (LAG) Configuration on 200/300 Series Managed Switches

 

Objective

A Link Aggregate Group (LAG) is used to link multiple ports together. LAGs multiply bandwidth, increase port flexibility, and provide link redundancy between two devices to optimize port usage. Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad) that is used to bundle several physical ports to form a single logical channel. LACP is also used to determine which ports of a dynamic LAG are active.

The article explains how to configure LAG Management, Lag Settings, and LACP on the 200/300 Series Managed Switches.

Applicable Devices

• SF/SG 200 and SF/SG 300 Series Managed Switches

Software Version

• 1.3.0.62

LAG Management

Step 1. Log in to the web configuration utility and choose Port Management > Link Aggregation > LAG Management. The LAG Management page opens:

Step 2. Click the respective radio button of the desired algorithm in the Load Balance Algorithm field. Load Balancing is a method that maximizes throughput on a network to optimize resource usage.

• MAC Address — Load balancing is performed based on the source and destination MAC addresses of all packets.

• IP / MAC Address — Load balancing is performed based on the source and destination IP addresses of IP packets and by the source and destination MAC addresses on non-IP packets.

Step 3. Click Apply.

Define Member Ports in a LAG

Step 1. Log in to the web configuration utility and choose Port Management > Link Aggregation > LAG Management. The LAG Management page opens:

Step 1. Click the radio button of the LAG you want to edit.

Step 2. Click Edit to configure the LAG. The Edit LAG window appears.

Step 3. (Optional) From the LAG drop-down list choose the LAG you want to configure.

Step 4. (Optional) Enter a name for the LAG in the LAG Name field.

Step 5. (Optional) Check LACP to enable Link Aggregation Control Protocol (LACP) on the LAG. LACP allows the LAG to have up to 16 ports.

Note: LACP can only be enabled before ports are added to the LAG.

Step 6. Choose the ports that you would like to add to the LAG in the Port List field.

Step 7. Click > to make the specified ports members of the LAG.

Step 8. Click Apply.

LAG Settings

Step 1. Log in to the web configuration utility and choose Port Management > Link Aggregation > LAG Settings. The LAG Settings page opens:

Step 2. Click the radio button of the LAG you want to edit.

Step 3. Click Edit to configure the LAG. The Edit LAG Settings window appears.

Step 4. (Optional) From the LAG drop-down list choose a LAG to configure. The Lag Type field displays the types of ports that comprise the LAG.

Step 5. (Optional) Enter a name for the LAG in the Description field.

Step 6. Click the radio button that corresponds to the desired LAG status in the Administrative Status field. The Operational Status field displays the current state of the LAG.

• Up — The LAG is up and operational.

• Down — The LAG is down and not operational.

Step 7. (Optional) Check Reactivate Suspended LAG to reactivate a LAG that has been disabled by locked port security or ACL configurations.

Step 8. (Optional) Check Administrative Auto Negotiation to enable admin auto negotiation. Auto negotiation is a protocol that allows two link partners to transmit transmission rates and flow controls to each other. The Operational Auto Negotiation field displays the current state of auto negotiation.

Step 9. Click the radio button that corresponds to the desired LAG speed in the Administrative Speed field. The Operational LAG Speed field displays the current LAG speed.

• 10M — The LAG uses a 10 Mbps speed.

• 100M — The LAG uses a 100 Mbps speed.

• 1000M — The LAG uses a 1000 Mbps speed.

Step 10. Check the box that corresponds to the desired LAG capabilities that are to be advertised in the Administrative Advertisement field. The Operational Advertisement field displays the speed that is advertised to the linked LAGs.

• Max Capability — All LAG speeds and duplex mode settings can be accepted.

• 10 Full — The LAG advertises a 10 Mbps speed and full duplex mode settings.

• 100 Full — The LAG advertises a 100 Mbps speed and full duplex mode settings.

• 1000 Full — The LAG advertises a 1000 Mbps speed and full duplex mode settings.

Step 11. Click the radio button that corresponds to the desired flow control in the Administrative Flow Control field. Flow control manages data flow between devices so that the data can be handled at an efficient pace. The Operational Flow Control field displays the user designated flow control setting.

• Enable — Flow control is enabled on the LAG.

• Disable — Flow control is disabled on the LAG.

• Auto-Negotiation — Auto-negotiation is used to determine if flow control should be enabled or disabled.

Step 12. (Optional) Check Enable in the Protected LAG field to protect the LAG through an uplink. This makes the LAG a protected port for layer 2 isolation between interfaces that share the same VLAN. A protected port does not forward any traffic to any other protected port on the same switch.

Step 13. Click Apply.

Setting Port LACP Parameter Settings

Link Aggregation Control Protocol (LACP) is used to prioritize ports on a LAG. A dynamic LAG can have up to 16 ports of the same type but only 8 can be active at one time. When a LAG has more than 8 ports, the switch uses LACP port priority to determine which ports will become active.

Step 1. Log in to the web configuration utility and choose Port Management > Link Aggregation > LACP The LACP page opens:

Step 2. Enter a LACP priority in the LACP System Priority field. The LACP priority is used to determine which device controls port selection to the LAG. Devices with a lower value will have higher priority. If both switches have the same LACP priority, the switch with the lower MAC address will be given control of port selection.

Step 3. Click the radio button of the port you want to edit.

Step 4. Click Edit to configure the port. The Edit LAG window appears.

Step 5. (Optional) From the Port drop-down list choose the port to configure.

Step 6. Enter a value for the port priority in the LACP Port Priority field. The lower the value, the higher the priority the port will have on the LAG.

Step 7. Click the radio button that corresponds to the desired LACP timeout. This determines the interval at which LACP protocol data units (PDUSs) are sent or received.

• Long — The interval between a sent or received LACP PDU and the next consecutive LACP PDU is long (30 seconds).

• Short — The interval between a sent or received LACP PDU and the next consecutive LACP PDU is short (1 second).

Step 8. Click Apply.

Link Aggregation for Synology NAS/Cisco SG 300 switches

fonte: http://www.kasson.com/bleeding_edge/?p=687

Link Aggregation for Synology NAS/Cisco SG 300 switches

A 1 Gb/s Ethernet connection can’t keep up with modern disks or the processors in Synology NAS boxes. For those of you with really deep pockets, there are Synology boxes with 10 Gb/s interfaces and 10 gigabit Ethernet switches to match, but for the rest of us, there’s link aggregation. Link aggregation, aka (in the Microsoft world) as Ethernet teaming, allows a computer (and, in this context, a NAS box counts as a computer) to bond together two or more Ethernet links so that they act as one higher-speed one. It also provides the ability to survive the loss of one link with no penalty other than decreased performance. The most common way of doing link aggregation is defined by an IEEE standard, 802.3ad. That’s the kind I’ll be discussing here.

To set up link aggregation, you need to make changes to your Ethernet switch to tell it to treat two ports as one aggregated connection, and to your computer, to do the same. Make just one change, and it won’t work. And, with the Synology boxes and the Cisco SG 300 switches, do things in the wrong order and it won’t work. That situation may obtain with other switches as well.

Through trial and lots of error, I’ve figured out how to make it all work.

First, connect the Synology box — hereafter called the NAS — to the switch with one Ethernet cable. Set up the network configuration for a fixed IP address. I suppose it might work with a DHCP-assigned IP address, but I think it’s safer to make it fixed.

Find two free ports on the Cisco switch. Set up link aggregation from Administration > Port Management > Link Aggregation > LAG management. A LAG is, I suppose, a Link Aggregation Group.

Click the selection box to the left of one of the LAG group entries, and then click on the Edit button at the screen.

LAG

 

 

 

 

 

 

 

Now you’ll see the window where you can create a LAG. Pick one of the two free ports.

cisco lag 1

Hit the arrow to move the port to the LAG.

cisco lag 2

And click the Enable check box next to LACP. Don’t miss this step!

cisco lag 3

Now add the next port.

cisco lag 4

Hit Apply, and close the window. Now log on to your NAS, open the control panel, click on network, and click on the Network Interface tab.

create bond syn 1

Click on the Create button to create the aggregated link. Accept the default IEEE 802.3ad option, and click next.

create bond sys 2

Make sue both LAN interfaces are checked.

create bond syn 3

The next screen will reflect the network configuration you’ve already entered. Hit Apply.

create bond syn 4

The window will go gray for a minute or two, which will seem like a long time. Have patience.

screen goes grey

Then the NAS will complain, because you haven’t connected to the LAG on the switch yet.

cant find link

Disconnect the NAS LAN port you’ve been using so far from the switch and connect it to one of the ports in the LAG. Connect the other NAS LAN port to the other port in the LAG. After a short while, the NAS will be happy.

success syn

Now go to the Cisco LAG screen and make sure it’s happy too.

cisco success

You’re done. Enjoy your high speed connection.