Add VDSwitchPhysicalNetworkAdapter

Is it possible to assign physical NIC to a VMHost to a particular VD uplink Port?

My distributed Virtual Switch has 4 uplinks for each host. My blade 4 physical network adapters, two are 10 gig and two 1 gig. I want to script a way for the 10 1 gig NIC (the one with the lowest MAC) is assigned to dvUplink1 the other 10 Gig NIC is assigned to dvUplink2. 1 1 gig NIC is set to dvUplink3 and the 2nd 1 gig NIC are they assigned to of dvUplink4. I know how to get a reference to the physical NIC appropriate hospitality, I just can't understand how to assign to a particular dvUplink on the DVS.

Any suggestions?

Thank you

If this is not done in the order that enter you them in the VMHostPhysicalNic parameter?

Tags: VMware

Local operating system support

You can install VMware vSphere PowerCLI 6.0 Release 3 on the following operating systems:

OS type

64 bit

Server

R2 Windows Server 2012
Windows Server 2008 R2 Service Pack 1

Workstation

Windows 8.1
Windows 7 Service Pack 1

Reference: for vSphere PowerCLI 6.0 Release 3 compatibility charts

Migration to Cisco 1000v with portgroup Vmnic (almost there!)

I am trying to automate the following steps so that I can configure networking for a host, end-to-end (using vCenter 5.1, PowerCLI 5.1 Release 2 Build 1012425 to PowerCLI 6.0 Release 2 build 3056836). The host has two network adapters physical, one of which (vmnic0) is obviously taken by vSwitch0 during initial installation. So, I need to:

(1) migrate physical vmnic1 a VDS (1000v)

(2) set the GRPE of ports uplink for vmnic1 in the "system-binding rising-vc02."

(3) turn on the VDS called "vc02-vmsc" vSwitch1 to a portgroup vmk0 management network.

(4) physical vmnic0 pass vSwitch1 a VDS, adding to the bond rising portgroup "rising-vc02 system-binding."

I can only reach 1-3. I can handle a party of 4), moving the 1000v vmnic0, but only in the portgroup of 'Unused_or_Quarantine_Uplink' and not the one I need.

Stripped of any handling error, this is the code I used (largely provided by)

http://blogs.Cisco.com/Datacenter/automate-migrating-ESX-host-interfaces-to-nexus-1000V )

http://www.virtuallyghetto.com/2013/10/automate-migration-from-virtual.html):

$esxihost = 'host-0201'
$vmnic = 'vmnic1'
$1000vName = 'cisco-1000v-data-centre-1'
$uplinkName = 'system-uplink-vc02'

# Get the 1000v object that that ESX host will be added to
$1000vObject = Get-VDSwitch | Where-Object -FilterScript {
    $_.name -eq $1000vName
}

# Get the ESX host object
$vmHost = Get-VMHost -Name $esxihost -Erroraction Stop | Get-View

# Create a DVS Configuration Specification object
$spec = New-Object -TypeName VMware.Vim.DVSConfigSpec

# Create a target host DVS Host member configuration specification and set the operation to add
$targetHost = New-Object -TypeName VMware.Vim.DistributedVirtualSwitchHostMemberConfigSpec
$targetHost.operation = 'add'

# Create a Pnic backing object in the target host
$targetHost.backing = New-Object -TypeName VMware.Vim.DistributedVirtualSwitchHostMemberPnicBacking

# Create a Pnic Device object
$pnic = $vmHost.Config.Network.Pnic | Where-Object -FilterScript {
    $_.Device -eq $vmnic
}

$targetHost.Backing.PnicSpec = New-Object -TypeName VMware.Vim.DistributedVirtualSwitchHostMemberPnicSpec
$targetHost.Backing.PnicSpec[0].pnicDevice = $pnic.Device

# Get the 1000V uplink object:
$uplinkObj = Get-VDPortgroup | Where-Object { $_.Name -eq $uplinkName }
$targetHost.Backing.PnicSpec[0].UplinkPortGroupKey = $uplinkObj.Key

# Set the target host to the ESX host object reference
$targetHost.host = $vmHost.MoRef

# Set the DVS configuration specification object host property, to the target host object reference we've created above:
$spec.Host = $targetHost

# Get the current status of the 1000v and set the version in the configuration specification version
$dvSwitch = Get-View -Id $1000vObject.ExtensionData.MoRef
$dvSwitch.UpdateViewData()
$spec.ConfigVersion = $dvSwitch.Config.ConfigVersion

# Run  the task
$taskMoRef = $dvSwitch.ReconfigureDvs_Task($spec)

# Get the status
$taskID = 'Task-' + $taskMoRef.Value
while((Get-Task -Id $taskID).PercentComplete -lt "100")
{
    $percentComplete = (Get-Task -Id $taskID).PercentComplete
    Write-Verbose "Percent Complete: $percentComplete"
    Start-Sleep -Seconds 2
}


# 3) Migrate vmk0 Management Network from vSwitch to the VDS with correct portgroup:

# Get the VMKernel port
$vNicManagement = Get-VMHostNetworkAdapter -VMHost $esxihost -Name vmk0
# Get the destination port group:
$vdPortgroupManagement = Get-VDPortgroup -VDSwitch $1000vName -Name 'vc02-vmsc'
# Set the physical NIC to use:
$pnicToUse = Get-VMHostNetworkAdapter -VMHost $esxihost -Physical | Where-Object { $_.Name -eq $vmnic }
# Migrate:
Add-VDSwitchPhysicalNetworkAdapter -DistributedSwitch $1000vName -VMHostPhysicalNic $pnicToUse -VMHostVirtualNic $vNicManagement -VirtualNicPortGroup $vdPortGroupManagement -ErrorAction Stop

The bit that will move to vmnic0 VDS service is:

# Get vmnic0 which is still connected to the vSwitch:
$lastNic = 'vmnic0'
$pnicToMove = Get-VMHostNetworkAdapter -VMHost $esxihost -Physical | Where { $_.Name -eq $lastNic }
# Migrate vmnic0 from vSwitch to VDS:
Add-VDSwitchPhysicalNetworkAdapter -DistributedSwitch $1000vName -VMHostPhysicalNic $pnicToMove -Confirm:$false

... but as I said, this only puts it in the Unused_or_Quarantine_Uplink group.

I tried to repeat the code above this vmnic1 against vmnic0 objectives, but this indicates that the host is already member of the VDS.

I suspect that the answer lies in a change of migrate ESXi host physical adapters specific dvUplink port | vBombarded but I had no luck so far.

Help appreciated on the final bit

Thank you.

I managed to solve this problem by using:

$config = New-Object VMware.Vim.HostNetworkConfig
$config.proxySwitch = New-Object VMware.Vim.HostProxySwitchConfig[] (1)
$config.proxySwitch[0] = New-Object VMware.Vim.HostProxySwitchConfig
$config.proxySwitch[0].changeOperation = "edit"
$config.proxySwitch[0].uuid = $1000vObject.key
$config.proxySwitch[0].spec = New-Object VMware.Vim.HostProxySwitchSpec
$config.proxySwitch[0].spec.backing = New-Object VMware.Vim.DistributedVirtualSwitchHostMemberPnicBacking
$config.proxySwitch[0].spec.backing.pnicSpec = New-Object VMware.Vim.DistributedVirtualSwitchHostMemberPnicSpec[] (1)
$config.proxySwitch[0].spec.backing.pnicSpec[0] = New-Object VMware.Vim.DistributedVirtualSwitchHostMemberPnicSpec
$config.proxySwitch[0].spec.backing.pnicSpec[0].pnicDevice = "vmnic0"
$config.proxySwitch[0].spec.backing.pnicSpec[0].uplinkPortgroupKey = $uplinkObj.key   

$vmhostRef = ($vmhost.MoRef.value).split('-')[1]
$_this = Get-View -Id "HostNetworkSystem-networkSystem-$vmhostRef"
$_this.UpdateNetworkConfig($config, "modify")

PowerCLI 6.0R2 bug with Import-Module-prefix?

Yesterday I installed a couple of nine Win2012R2 servers and of course installed PowerCLI 6.0R2.
In order to avoid multiple commands with the same name, we use the--Prefix setting for the modules. It worked great in R1 but I am facing problems with R2.
Load the modules with code below:
$VMwareModules = 'VMware.VimAutomation.Core', 'VMware.VimAutomation.Vds'
foreach ($Module in $VMwareModules) { }
if (! (Get-Module | ? {$_. (({Name -eq $Module})) {}
Try {
Import-Module -Nom $Module -Prefix "VMW"
}
Catch {
$ErrorMessage = $_ . Exception. Message
breaking
}
}
}

When running Get-Module now the modules but show the Basic module shows all ExportedCommands (which he did in R1).
Basic modules shows too, now that 'script' instead of 'manifesto', as in R1.
Not sure if this has anything to do with this.

If we compare the number of orders 'Raphael' in R1 and R2, missing 300 orders for the Basic module in R2.

Is this a bug? Is there a solution?

R2:
PS C:\ > get-module
Version of Moduleinfo name ExportedCommands
---------- ------- ---- ----------------
Script Initialize-VMware_VimAutomation_Vds 0.0
Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Con...}
Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, add-Type, Clear-Variable, Compare-Object...}
VMware.VimAutomation.Core script 6.0.0.0
Clear VMware.VimAutomation.Sdk 6.0.0.0
6.0.0.0 binary VMware.VimAutomation.Vds {add-VDSwitchPhysicalNetworkAdapter, add-VDSwitchVMHost, E...
PS C:\ > get-vitoolkitversion
PowerCLI Version
----------------
VMware vSphere PowerCLI 6.0 Release 2 build 3056836
---------------
Component versions
---------------
VMWare AutoDeploy PowerCLI component 6.0 build 2358282
VMWare ImageBuilder PowerCLI component 6.0 build 2358282
VMware vSphere PowerCLI component 6.0 build 3052101
VDS's VMware PowerCLI component 6.0 build 3052101

PS C:\ > (get-command * vmw *) .count
33

R1:
PS C:\ > get-module
Version of Moduleinfo name ExportedCommands
---------- ------- ---- ----------------
Script Initialize-VMware_VimAutomation_Vds 0.0
Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Con...}
Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, add-Type, Clear-Variable, Compare-Object...}
VMware.VimAutomation.Core manifesto 6.0.0.0 {Add-PassthroughDevice, add VirtualSwitchPhysicalNetworkAd... }
Clear VMware.VimAutomation.Sdk 6.0.0.0
6.0.0.0 binary VMware.VimAutomation.Vds {add-VDSwitchPhysicalNetworkAdapter, add-VDSwitchVMHost, E...
PS C:\ > get-vitoolkitversion
PowerCLI Version
----------------
VMware vSphere PowerCLI 6.0 Release 1 build 2548067
---------------
Component versions
---------------
VMWare AutoDeploy PowerCLI component 6.0 build 2358282
VMWare ImageBuilder PowerCLI component 6.0 build 2358282
License of VMware PowerCLI component 6.0 build 2315846
VMware vSphere PowerCLI component 6.0 build 2548068
VDS's VMware PowerCLI component 6.0 build 2548068
PS C:\ > (get-command * vmw *) .count
12 p

Hello

First of all, I must say that you are right. This is a regression introduced in 6.0 R2 caused by updates in the manifesto of the module which target to attack another bug. Let me give you more explanation in detail on the specifics of the module VMware.VimAutomation.Core.

Binary VMware.VimAutomation.Core is always snap-in in 6.0 R1, 6.0R2 and 6.0 R3. Which is related to internal constraints that will be overcome in the next version and the binary file is converted to module as it should.

As binary VMware.VimAutomation.Core is pluggable PowerCLI makes it look like a module declaring a manifest module which load the snap and load so its commands to load this module 'false '. The VMWare.VimAutomation.Core module so manifest module powershell that refer to a script that loads the binary VMWare.VimAutomation.Core snap. Script files, the manifesto and that loads the snap are in the module folder: '\Modules\VMware.VimAutomation.Core '.

Now the problem you face is that, in 6.0R1, the script that loads the snap was referenced in NestedModules module manifest, which means that all orders imported as nested module are imported into the scope of the module session. This makes the component controls snap to consider as a command module and that's why your use case has worked with 6.0R1. The problem with this is that if someone calling Remove-Module command for this module it deletes the orders of the current session, and if Import-Module is called again in the same session, that it will fail with an error "The VMware.VimAutomation.Core is already added," so no commands are loaded once the module is removed from the current session. Because of this bug, we decided not to reference the script component snap load in NestedModules but in ModulesToProcess of the module manifest. When it is referenced in the ModulesToProcess that makes the script commands to be loaded in the scope of global session which means that these commands are removed from the session when Remove-Module is called and if Import-Module is called once again he will not fail because the module manifest try again to load the sanp-in. When the controls are respectively in the context that they are not affected by the specification of modules and that is why they cannot be imported with the desired prefix you want.

To be honest we didn't know this side effect when we discussed the initial bug with Remove-Module. All these problems will be solved in the next PowerCLI release when binary VMware.VimAutomation.Core will become the module. Until then, I suggest you workaround with fixation of the VMWare.VimAutomation.Core manifest file. To do this you have need open and change of \Modules\VMware.VimAutomation.Core\VMware.VimAutomation.Core.psd1

the following way:

1. set ModuleToProcess on a string is empty

2. put NestedModules to @('VMware.VimAutomation.Core.ps1')

This will make the module to behave in the same way as 6.0R1

Kind regards

Dimitar Milov

Migrate standard network switch to VDS

Hello
I intend to migrate little my clusters that are running in a standard switch to DVS. Need help to automate this process.
My scenario is:
In a 15cluster environment are present 5 are already running in DVS
but 10 clusters are still a standard switch so I need to migrate the
already existing DVSwitch.
By taking a cluster of 10node as an example.
(1) mgmt and vmkernel are on a vswitch (ex: vswitch 0)
[vswitch 0 - connected with 2 vmincs]
(2) virtual machine in a vswitch portgroup (Ex: vswitch 1)
[vswitch 1 - connected with 2 vmincs]
On all groups, we need to migrate only machine virtual portgroup
or vmnetwork (ex: vswitch 1) to off-network vmkernel mgmt DVs.
My plan:
First add all cluster hosts to DVswitch
Remove all a redundant vmnic (ex: vmnic3) connected to the machine virtual portgroup. (Ex: vswitch) 1 and adds it to DVswitch.
Now migrate all virtual machines connected to a standard switch to dvs. (Here I hit)
Is it possible if VLAN 10 (standard switch) then consists of 5 virtual machines
check the VLAN 10 DVS and portgroup network set to 10 VLAN adapter on the
SMV (I mean can we compare VLAN ID on VSS and VDS and inspiring than us)
need to migrate virtual machines to a DVS.)
As below:

If it works correctly then you have to check the State of all virtual machines (ignore power VM off) ping
If ok then proceed to map the second network card (ex: vmnic4) VSS for VDS.
Use the Script:
```
# ESXi hosts to migrate from VSS to VDS
$vmhost_array = @("host1","host2")
# Adding Hosts to existing VDswitch
$vds = Get-VDSwitch -Name "SM_UAT"
foreach ($vmhost in $vmhost_array) {
# Add ESXi host to VDS
Write-Host "Adding" $vmhost "to" $vds_name
$vds | Add-VDSwitchVMHost -VMHost $vmhost | Out-Null
# Migrate pNICs to VDS
Write-Host "Adding vmnic2 to" $vds
$vmhostNetworkAdapter = Get-VMHost $vmhost |Get-VirtualSwitch -Name "vswitch1" |select -ExpandProperty Nic |select -First 1
$vds | Add-VDSwitchPhysicalNetworkAdapter -VMHostNetworkAdapter $vmhostNetworkAdapter -Confirm:$false
# Migrate VMs from VSS to VDS
Write-Host "migrating vms from VSS to VDS"
}
```
Maybe try like this

# ESXi hosts to migrate VSS to VDS

$vmhost_array = get-VMHost-name 10.50.37.31

# get existing VDswitch

$vds = get-VDSwitch-name "Pre-production".

foreach ($vmhost to $vmhost_array)

{

# Add ESXi hosts service VDS

Write-Host-object 'Add' $vmhost 'to' $vds

$null = $vds |

Add-VDSwitchVMHost - VMHost $vmhost

# Natachasery to VDS migration

Write-Host-object «first extraction vnic connected to vswitch»

$vmhostNetworkAdapter = get-VMHost $vmhost |

Get-VirtualSwitch-name "vswitch1 |

Select-Object - ExpandProperty Nic |

Select-Object - 1 first

Write-Host-object "Removing vswitch vnic.

$vmhost |

Get-VMHostNetworkAdapter-name $vmhostNetworkAdapter |

Delete-VirtualSwitchPhysicalNetworkAdapter-confirm: $false

Write-Host-Object "RΘcupΦre removed vnic in a variable.

$Phnic = $vmst | Get-VMHostNetworkAdapter-physics - name $vmhostNetworkAdapter

Write-Host-object "adding vmnic (redundant) to ' $vds

Add-VDSwitchPhysicalNetworkAdapter - DistributedSwitch $vds - VMHostPhysicalNic $Phnic - confirm: $false

# Migrate virtual machines from VSS for VDS

Write-Host-Object «RΘcupΦre virtualPortgroup vswitch info»

$vssPG1 = $vmhost | Get-VirtualPortGroup - VirtualSwitch "vswitch1.

Write-Host-object "migration of VSS for VDS vms."

foreach ($vssPG to $vssPG1)

{

$dvsPG = $vds |

Get-VDPortgroup |

Where-Object - FilterScript {}

$_. ExtensionData.Config.DefaultPortConfig.Vlan.VlanId - eq $vssPG.VlanId

}

$vmhost |

Get - VM |

Get-NetworkAdapter |

Where-Object - FilterScript {}

$_.NetworkName - eq $vssPG.Name

} | Together-NetworkAdapter NetworkName - $dvsPG.Name - confirm: $false

}

Migration VMkernel VDS1 to VDS2 e-cards

What is the best way to add VMkernel virtual cards when a host migration using VDS vCenter1 to vCenter2? I have attached a sample script that I use for the process. The last command Add-VDSwitchPhysicalNetworkAdapter fails with an error "value cannot be null.
For background, I have a source vCenter Server (version 5.0) and a target vCenter Server (version 5.5). I have a hot migration from a host that uses VDS between vCenter1 and vCenter2. If I run the script step by step, everything works as expected until the command Add-VDSwitchPhysicalNetworkAdapter. I can then complete the process manually by using the following in the vSphere Client process:
Hosts and Clusters-> select host-> Configuration-> network-> vSphere Distributed Switch-> manage e-cards (for the appropriate VDS)-> add-> existing migration of virtual cards
After completing the manual steps above, I can then remap the VMs and then remove the old VDS (which no longer exists).

Something like that

$vdpgNames = 'Network management', 'Network storage', 'vMotion Network. "

$vdpg = get-VDPortgroup-name $vdpgNames - VDSwitch $TargetVDS

Add-VDSwitchPhysicalNetworkAdapter - DistributedSwitch $TargetVDS - VMHostPhysicalNic $vmhostNetworkAdapter - VirtualNicPortgroup $vdpg - VMHostVirtualNic $vmk0, $vmk1, $vmk2 - confirm: $false

Script adding a host to a distributed switch does not

It's weird and I'm sure it's something simple. I've created a script that configures the NTP and the syslog on a host computer. I added on the configuration of the standard vswitch0 and part works fine. I set the MTU, add a vMotion and port FT and that part works fine. I wanted to add on a section of code to add the host of our distributed switch. Environment vSphere 5.5 U2, switch is a distributed switch 5.5. For some reason, the code is not error at all but just does nothing. However, if I paste the code into a Powershell window it works fine. Same code, same host, same switch. Ideas as to why it works manually by pasting the code into a window, but does not work, I use the script itself. Here's the code that does not work in the script:
#Adds vmnic5 and vmnic6 for the distributed switch
Write-Host
Write-Host «Addition of $VMHost to the switch distributed $vds...» "- ForegroundColor"green ".
Disconnect-VIServer *-confirm: $false #earlier part of the script is directly connected to the host
SE connect-VIServer $vcenter | Out-Null #$vcenter variable created earlier in the script
Get-VDSwitch $vds | Add-VDSwitchVMHost-Server $vcenter - VMhost $VMhost #$vds and $VMhost variables collected earlier in the script
$vmnic5 = get-VMHost $VMhost | Get-VMHostNetworkAdapter-physics - name vmnic5
$vmnic6 = get-VMHost $VMhost | Get-VMHostNetworkAdapter-physics - name vmnic6
Get-VDSwitch $vds | Add-VDSwitchPhysicalNetworkAdapter - VMHostPhysicalNic $vmnic5 - confirm: $false
Get-VDSwitch $vds | Add-VDSwitchPhysicalNetworkAdapter - VMHostPhysicalNic $vmnic6 - confirm: $false
Seems pretty simple, but for some reason it just doesn't work. Any ideas?

When you load the script into an editor (PowerShell ISE for example) and can run from there, run the cmdlets vDS?

I have an ipod touch 128 GB... but I'm almost to reach its maximum. I want to do is buy a new ipod touch 128 GB and add new music without synchronizing the entire library to it... I have 2 ipods in conjunction with other copies

I have an ipod touch 128 GB... but I'm almost to reach its maximum.

I want to do is buy a new ipod touch 128 GB and add new music without synchronizing the entire library to it... I have 2 ipods in conjunction with the other copies of the other.

is this possible?

What should I do?

Matt

When you get the new iPod, you can use iTunes on your computer to select and synchronize the music you want on it, in the same way that you synchronize your current iPod - your iTunes will recognize them as different devices and will remember your choice of synchronization for each, it will not (unless, for example, you restore the backup of your current on her iPod) put the same content on both.

(I asked for your post be moved to the iPod Touch forum, where you have posted is the iPad forum use.)

The screen add people faces a (~ 1600) much just show as squares of white, grey

Hello

I was going through my photo library (running 2.0 on Sierra Photos) cleaning and marking of the people. I got far just about every face on the left is a square white, gray. If I add this person, the area where the image would be just rotates the circle of progress.

Any idea on what is happening? I really miss the ability in iPhoto in order to have a Smart Album based on a photograph with a person "without name".

Thank you, Tim

That is a disused here bug that if you click on the x to remove a face, you end up with a tile empty - I hope that this will be fixed in a future Apple 9tell on the bug to improve its priority - http://www.apple.com/feedback/photos.html of output) and I hope that the patch will fix these old problems as well as properly - not advancing It is better to stop the removal of the faces until this problem is corrected

LN

Add dictionary

Hello.

I have a question: I would like to add additional dictionaries in the Sierra of MacOS.

Initially, some trouble with record find "dictionaries". But this problem is solved here: where is the dictionary in the Sierra folder

After that, I saw:

(It seems different from El Capitan).

In the folder "CoreDataUbiquitySupport" can't get the files with the .dictionary extension. And throughout the system (I used Spotlight) I cannot find these files.

When I try to add my files with extension .dictionary in "Dictionaries" folder - nothing happened.

Please, help me. What should I do?

Thank you.

I found the files .dictionary you are looking for here:

/ System/Library/assets/com_apple_MobileAsset_DictionaryServices_dictionaryOSX/37 7ca105ade0203e0c89af6538f7b8ab0204dfba.asset/AssetData/Oxford English.dictionary thesaurus

/ System/Library/assets/com_apple_MobileAsset_DictionaryServices_dictionaryOSX/5 has a689bfd471f943f70bd220ec2ed3849b7dbec3.asset/AssetData/Oxford Dictionary of English.dictionary

/ System/Library/assets/com_apple_MobileAsset_DictionaryServices_dictionaryOSX/f9 384c21fc7d64ad09992ad8bebbbfac16ad6a9d.asset/AssetData/Apple dictionary

can I still add to apple care if the warranty has expired?

can I still add to apple care if the warranty has expired?

No, if it is out of warranty, if it is for a Mac: http://www.apple.com/support/products/mac.html

The AppleCare Protection Plan can be purchased as long as your Mac is still covered by the limited warranty of one year.

Add people

So, I've updated for Mac OS Sierra. Have been using the Photos app since it was released and spent a lot of time organize using faces and now I have hundreds of photos to browse again and put names to people.

I'm in add people and get 632 white picture with numbers under. To be able to identify the people, if I add them, and then double-click it to view more deep - no images do not face appear.

I already went through and added all the images of virgins like that and then hidden, now, today, I have another more than 600 of them. Any ideas?

I NSB Sierra since the evening he lauched and use my Mac every day for that if he should have had time to complete the analysis now.

Thanks & Hello all

but he has finished scanning and - when you launch Photos and click on people get you people or a text for scanning status?

LN

"Add a printer" crashing

Pref systems > Scan & print

I can open the Scan & Print window under system preferences; However, when I click (+) to add a new printer, the Add Printer dialog box opens a second and quits immediately. This behavior started after I removed an existing printer.

Does anyone know how can I fix?

Reset did not help.

Error log shows:

Process: AddPrinter [406]

Path: /System/Library/CoreServices/AddPrinter.app/Contents/MacOS/AddPrinter

ID: com.apple.print.add

Version: 8.3 (405.2)

Generation information: PrintCenter-405002000000000 ~ 1

Code type: X 86-64 (Native)

Parent process: launchd [177]

User ID: 501

Date/time: 2016-10-05 16:30:40.801-0700

OS version: Mac OS X 10.8.5 (12F2560)

Report Version: 10

Crashed thread: 0 dispatch queue: com.apple.main - wire

Exception type: EXC_BAD_ACCESS (SIGSEGV)

Exception codes: KERN_INVALID_ADDRESS at 0x000000010e05ca8f

Reset the printing system

Why can't add sounds to mail to Sierra

After the upgrade to Sierra, I would add is no longer a 'personal' sound of my files to act as my 'new message '. The sound folder is locked and I have, even as an administrator, can't unlock it or add sounds in the folder. All I have now is a drop-down list of predetermined choice of Apple, and none of these things include the addition of new sounds. Preference once gave me the choice to go to my files, I have more choice. Can someone tell me how to add my own sounds?

MACBOOK PRO15.

Intel core i7 to 2.7 GHz

8 GB memory

as it is in this matter and, of course MAC OS Sierra 10.12.

Greetings gklav,

Thank you for using communities of Apple Support. It seems that you want to use a custom sound in Mail when a new message arrives. I recommend reading this article, it explains how the feature works and what is available.

New sound of messages

The sound to play when you receive messages. To make a sound sampling, click on the context menu, and then select a sound.

Mail for Mac: General preferences in Mail

Take care.

Add VDSwitchPhysicalNetworkAdapter

Similar Questions

Local operating system support

Maybe you are looking for