ESXi VNIC speed fell after upgrade 2.2.2c

Similar Questions

• Need help... Internet speeds crawl after upgrading Vista to 7 Ultimate on HP tx 2000

  Hi all

  I was wondering if I could get help about an annoying problem that arose.

  I've recently upgraded the OS on my HP tx2000 tablet PC from Vista Home Premium to Ultimate 7.

  Internet speeds were very well then; I decided to investigate why the supplied remote control does not work with the new operating system.

  I downloaded a driver from the HP website was supposed to define the working distance with 7 Ultimate.

  It was the worst mistake I could never do; my missing just average Internet speed.

  Later, I thought it was probably due to the pilot that I had installed.

  Internet speeds have continued to be excruciatingly slow, so much so that I decided to reinstall 7 Ultimate.

  But the annoying problem persists, even after a couple of relocation of the operating system.

  I tried to change the settings for Windows Update in order to do not for download ' n automatically installs the driver for remote control.

  Don't even know if this RC pilot is actually one rotten; If this is not the case, what else could be the cause of slow Internet connection?

  But the problem persists...

  I wonder if anyone here has had a similar problem, or if someone could give a useful overview.

  Really need your help now, I'm totally lost... Thank you in advance and wish you all the best,.

  See you soon,.

  Amarnath.

  Update:

  Problem solved. Gites helped.

  Network drivers for Vista to run the tablet.

  But really the HP tx 2000 can be very irritating sometimes.

• ESXi hosts disconnected/no response in Vcenter after upgrade (4.1 = > 5.5)

  Hello. I'm upgrading our current infra (hosts/Essential licensing Vcenter / 3 ESXi 4.1).  vCenter Server has been upgraded OK, so I started to esxi upgrade hosts one by one.

  Upgrade process is OK, but after the reboot, upgrade marked as "not responding" in vsphere client server. I could ping this host and connect via ssh.

  When you try to reconnect the client host, got a strange error "this edition of vCenter only supports 3 host (s) in the inventory. After 3-4 hours of nothing to host

  has begun to show ok. After upgrading a second host, the same situation. I don't understand, how to solve it without waiting for another 4 hours.

  Restart of host management agents does not help.

  I remember I have a similar situation in the past where the number of licenses does not update as expected, i.e. required some time. What helped was to restart the server vCenter Server in my case. Maybe worth a try!

  André

• Can't connect after upgrade to ESXi 5

  After upgrading ESX 4.0.0. for ESXI 5, we are not able to connect console to esx server, there are two choices F2 or F12. I have already set up all the parameters F2, as Ip address, host name...

  Could you please tell how to get or connect to the console command root? even I can't use mastic to apply commands.

  Kind regards

  Ahmed

  Hello.  Even if SSH has been activated before the upgrade then reactivated later.

  Select F2 and log in as root.

  In the menu, select Troubleshooting Options

  Select enable the ESXi environment and press ENTER - this allows the shell local ESXi (use Alt - F1 to access)

  Select enable SSH and press ENTER - this allows SSH

  SSH can also be activated from vSphere Client host-> Configuration-> Security Profile

  This KB should help http://kb.vmware.com/kb/1017910

  I hope this helps.

  Hersey
  

• Reader SuperDrive does not burn after upgrade of el capitan

  Almost immediately after upgrading a mac mini end of 2014 to el capitan (10.11.2), the superdrive has lost his ability to write DVD. It is recognized by the system and can read DVDs fine, but any attempt to burn files or an ISO image on a disc breaks down.

  The superdrive even happily burn on the same media on other macs in Yosemite (I checked several times), but he stubbornly refuses to do it on el capitan. The same mac mini was happily burn DVDs on the same media with the same superdrive on Yosemite, just before the upgrade to 10.11.2.

  Now, with el capitan, attempts to burn ISO images fail with the message:

  "Error burn image to disc: the disc can't be burned; It might be incompatible with this disc drive. Please, try a different brand of disc, or try burning at a slower speed. »

  Burn files fail with the message:

  "The disc can't be burned because the device failed to calibrate the power level of laser for this media."

  Any ideas on how to solve this problem would be appreciated.

  Reader SuperDrive material report:

  OPTIARC DVD RW AD - 5630 HAS:

  Firmware revision: 1CHQ

  Interconnection: USB

  Burn support: Yes (Apple shipping Drive)

  Cache: 2048 KB

  Read DVD: Yes

  Write: CD - R, - RW

  Write: DVD - R, -r DL, - RW, + R, + R DL, + RW

  Write strategies: CD - TAO, SAO - CD, CD - Raw, DVD - DAO

  Media:

  Type: DVD - R

  ID: CMC MAG AM3

  Vacuum: Yes

  Erasable: No.

  Replaceable: Yes

  Editable: Yes

  Write speed: 2 x, 4 x, 6 x, 8 x

  Try these in order to test your system after each see if it is back to normal:

  1. a. reset the PRAM and NVRAM on your Mac.

  b. Macs with Intel processors: reset of the controller (SMC) system management

  2. restart the computer in Safe Mode, and then restart again, normally. If this does not help, then:

  HD recovery start: restart the computer and after the buzzer, press on and press and hold the

  COMMAND and R keys until it appears the Utilities menu screen.

  3 fix the hard disk and permissions: select startup drive in the Utilities menu utility. Fix the hard drive and the permissions as follows.

      When the recovery menu appears, select disk utility and press the continue button. After loading disk utility select it

      back from Macintosh HD entry of the list on the left.  Click first aid button in the toolbar. Wait for the operation

      ends, then quit disk utility and back to the main menu.

  4 reinstall OS X: restart from HD recovery Select reinstall OS X from the Utilities menu, then click on the continue button.

  Note : You will need an active Internet connection. I suggest to use Ethernet if possible because it's three times faster than wireless.

  
  

• Second monitor is not detected after upgrade to Windows 10

  After you have installed Windows 10 upgrade Windows 7, my second monitor is no longer functional. The computer is an HP Touch Smart 610-1065qd. I connect on the second monitor through a USB 2.0 Port Replicator 2005pr HP. The Replicator appears as a drive when you look at this PC and an arbitrator in him like HP USB DOCK, as it did in Windows 7. The Replicator seems to work, I can't access the SSD on the device and use a wireless mouse. The receiver is connected to the port replicator. The second monitor, also connected to the Replicator, as it was before the upgrade. Now the system is unable to detect this monitor. The MANAGER of peripheral DEVICES, MONITORS, indicates there is a monitor Active, listed as "PnP monitor" generic Device Manager displays a second monitor as a hidden device. Identified as a "generic PnP monitor' and the State of the device is"currently, this hardware device is not connected to the computer. (Code 45) ». In Windows 7, I don't remember the second monitor listing. USB and the DISPLAY NETWORK DEVICES, the entry is USB PORTS port REPLICATOR 2.0 HP 2005pr. Under GRAPHICS cards, there are two lists. The first is an adapter named "AMD Mobility Radeon HD 5570". This corresponds to my video card. The second adapter named "glance speed Boost. I believe that Ancestry.com can installed this. "This device is working properly" is the condition for both cards. I manually checked new drivers for all components. There is no effect. Then, I went to HP and downloaded the most recent Setup to monitor. I then tried to load the drivers and monitoring software. I also loaded the screen in compatibility mode, then in compatibility mode for Windows XP SP3, then compatibility for Windows 7 and finely mode as a regulator. As a result, I tried the same process with the original disc. After each test, I rebooted the system. Still unable to detect the second monitor, nothing in Device Manager and unable to detect a new monitor on screen. I attempt to change the Projection. He also, had no effect on the display. Then, I deleted graphics cards. First of all, the adapter "AMD Mobility Radeon HD 5570", which corresponds to my video card. Second, the "Speed Boost glance. This also, don't give not any what on second monitor display. Even if it is visible only when show it hidden devices is checked. Any suggestions will be appreciated.

  I finely found a fix for the problem to my question; Second monitor, not detected after upgrade to Windows 10. Not the one I was hoping. It turns out that the fault was with the HP 2005pr USB 2.0 Port Replicator. It seems that the driver may be at fault. After more than a month of waiting, I decided to replace the duplicator. I decided to buy a Port adapter to replace the duplicator. What is much less expensive experiment and see if it was infecting the duplicator. It turned out that my second monitor is back and healthy. I decided to continue to use the port adapter and buy a USB Hub to replace this part of the duplicator. I no longer use the HD Audio output, after replacing the old speakers with Bose USB speakers some time ago. I thank everyone for help.

• HP ENVY tilted 23-k000a Touch: terribly slow internet wifi after upgrade to win8.1 - ENVY tilted 23-k000a Touch

  I bought a few weeks ago.

  After upgrading to win8.1, I noticed the speed of internet was slow, I'm on a connection "Ultra-fast VDSL" yet all downloads by wireless are 15 to 25kbs max.

  If I connect the cable to the modem and disconnect the wireless connection, I get 200 to 300 kbs as I should, but then my game of Ryan box can't find my computer, as soon as I reconnect wireless it can.

  OK, maybe two questions here, but to start I would like to help to get the connection wireless operating at the speed it should.

  Thank you, John

  Maybe I should say kBs...

• WTR320N still slow after upgrade

  Today, I upgraded my LAN 10/100mbps to 100/1000 Mbps Wireless LAN using the Linksys WTR320N with. The initial tests took place without problems. The small local network set up with 2 laptops, router and modem worked well and I plugged in the other systems.

  During the test, the speed of the internet was as before, instantaneous loading of most of the pages (Facebook, Youtube, etc.) and reaches the maximum capable speed, which is 23MBps with a low ping about 30.

  Now, with the entire network, the internetspeed is not top 20MBps more, it sticks to 15-17, which is a loss of 6 Mbps on my connection. After checking on various topics on other forums, I upgraded the firmware of 1.0.0.3 for 1.0.0.4. Who gave a small improvement, but I can't yet reach my speed max, neither a decent ping and pageload time.

  I'm a cable internet provider that requires no password/username to log, so it is a permanent connection. MTU is 1500, and because I don't know what it is (I've seen the expression and change it to 1300/1350. a few times looking for a solution).

  No idea how I can speed up the loadtimes and the internetspeed?

  [EDIT] problems are both on cable in Wi - Fi. The signal strength of the wireless is maximum and never given wired connections problems before.

  Change the MTU to 1365.

  You have already updated the Firmware of the router.

  After upgrading the firmware on the router, it is recommended that you must reset the router and reconfigure the router.

  Press and hold the reset button on the router for 30 seconds. Release the reset and wait for 10 seconds. Power cycle the router and reconfigure the router.

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G

• Keyboard problem after upgrade to 6.0

  Hello everyone

  I used 5.5 of Vmware Vsphere ESXI and Vcenter 5.5 without any problem of keyboard on the remote console on the guest operating system (win 7) after upgrade to esxi, vcenter 6.0 and 6.0, I have problems with the keyboard on the guest remote operating system, note I use french keyboard.

  french keyboard is also used by the operating system remotely.

  How can I solve this problem, so when I try the console remotely on the guest operating system display does'nt English keyboard us keyboard

  Thank you

  the problem is still persisting when using the web console, but when you use the remote console MRC the keyboard works normally

• Lost access to the volume after upgrade 4.1

  Setup

  1 x HP c7000 blade box

  3 x HP BL460cG6 with dual Xeons 5540 and 48Gb of RAM, cards ISCSI HBA, QLogic

  3 x HP P4300 Lefthands

  4 x 3020 Cisco switches for blade in the back the c7000, 2 x dedicated to iSCSI traffic

  vSphere 4.1 Server

  The problem

  We went through the entire process of upgrading our server for vSphere 4.0 to 4.1 to manage a stand-alone ESXi 4.1 system, so our attentions turn to our 3 blades running ESXi 4.0u1 we used the built in Update Manager, downloaded the 4.0 to 4.1 upgrade file and we have improved our first blade and it did not notice problems as there put servers have was little used those.  We then upgraded the second and moved our main mail on her server.

  It was when we did that we started getting errors when people were losing connection to the exchange server, after some research we've seen of the event and we have been to see the error:

  "Lost access to the volume because of connectivity issues."  Recovery attempt is underway and the results will be available shortly"

  Then 10 seconds later we get the message:

  "Successfully restored access to the volume due to connectivity problems."

  This error only occurs on the blades of 4.1, we have restored a blade on 4.0 and errors are not displayed and no errors were reported with the servers on this blade.  As far as we can say it is not a network problem since all blades for iSCSI traffic flows on the same switches to the Lefthands, and we were losing the connection to volumes on the two Lefthands.

  We have a call connected with HP about this, but from the Yes, we cannot determine what is causing this problem and how to solve.

  So any help is greatly appricated

  Thank you

  Dave

  This is due to a combination of ESX(I) 4.1, QLogic and version Lefhand SAN/IQ 8.5 with the 10092-00 patch version. I did a blogpost on his problem:

  http://yuridejager.wordpress.com/2011/02/07/lost-access-to-volume-error-with-hp-lefthand-san-storage-after-upgrading-to-vmware-vsphere-41/. I hope this helps.

• Time Machine does not work after upgrade to Sierra

  The Time Machine (TM) fail to start backup and there is still "preparing backup...". "for more than an hour. This right after upgrading to Mac OS Sierra.

  Another weird thing happens to the toolbar of the Mac Mail. The Junk button is replaced by another button. trying to put back in place, but remove the button become a button.

  Please help with the backup problem mentioned above. Thank you much in advance.

  How long have you waited? After a new installation, it must be a fair while even with a SSD to prepare the first backup due to the number of modified files.

  Make sure the TM drive is in the list of items excluded from Spotlight indexing. ICloud newsletter and other cloud services.

• Not able to scan with the preview after upgrade from Mac OS Sierra...

  After upgrading to Mac OS Sierra. I'm unable to use the preview to scan.  Before this upgrade, it worked fine.  The HP scanner software does NOT work something like OS 10.8 or 10.9.  Preview worked perfectly so far.  If anyone knows how to solve this problem, your contribution will be greatly appreciated.  Thanks in advance.

  Have you tried scanning with Capture of Image instead? It worked for me.

• Projector does not work after upgrade from Sierra

  My projector does not work after upgrade to Sierra. Or search in Outlook (I use outlook for Mac due to having MS 365 for labour) or the search function in the finder. I use this all the time and need this feature back. I tried to reindex spotlight and nothing. Anyone has any ideas.

  Try to rebuild Spotlight rebuild the Spotlight to your Mac - Apple Support index

• Lost after upgrade ios10 notes

  How is it possible to recover all the local notes that disappeared after upgrade to iOS 10?

  (On the iPhone 6)

  Thanks for help :-)

  Marco!

  If you have backed up your data, as Apple recommends the update to iOS 10 - official Apple Support, you can restore your iPhone, iPad or iPod touch backup - Apple Support