(Solved) Issue with 2012 & 2012 r2...Creating New Virtual Desktop Collections Fails

Hi all, thought I would share a fix I found out after hours of pulling my hair out.
If you get the following error when creating a new RD Collect: "The virtual desktop must be in a stopped state: Could not identify the state of the virtual desktop. Ensure that the RD virtualization host server is available on the network and
the virtual desktop is shut down"
ENSURE your RD Connection Broker and RD Virtualization Host are both either 2012 or 2012 r2. I was unable to create new VD Collections until I moved my Connection Broker from a 2012 box, to a 2012 r2 box. (My RD Virt Host is 2012 r2.) Once I did that,
everything worked fine.

Hi,
Thanks for your good sharing.
I think it will help the people who have the same issue.
Have a nice day.
Regards.
Vivian Wang

Similar Messages

RDS 2012 - Virtual desktop collection with powershell and custom answerfile fails on VDI deployment

Hi Guys,
I try to deploy a new virtual desktop collection with Win8 VDI's (pooled/managed) based on a custom answer file. Everything needs to automated so working with the server manager is not an option, that's why the answer file is needed.
The lab environment is based on Windows Server 2012 and Win8 Enterprise only. So functional level etc. is off course Windows Server 2012.
I Use the following command:
New-RDVirtualDesktopCollection `
-CollectionName "Pooled Managed Win8" `
-Description "This collection contains Pooled and Managed Win 8 VDI machines." `
-OU "VDI" `
-ConnectionBroker "RDSCB01.lab.local" `
-PooledManaged `
-CustomSysprepUnattendFilePath "\\hyper02\_Unattend\OOBE-only.xml" `
-VirtualDesktopAllocation @{"hyper02.lab.local"=3} `
-VirtualDesktopNamePrefix "Pooled-Win8-" `
-UserGroups "lab.local\domain users" `
-MaxUserProfileDiskSizeGB 1 `
-VirtualDesktopTemplateHostServer "hyper02.lab.local" `
-VirtualDesktopTemplateName “_WIN8-Template” `
-UserProfileDiskPath "\\hyper02.lab.local\_UserProfileDisks" `
-StorageType LocalStorage `
-LocalStoragePath "E:\_VDI" `
-Force `
-Debug
$error[0]|format-list -force
I tried multiple answer files, but even with this simple one it fails:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>nl-NL</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserAccounts>
<AdministratorPassword>
<Value>UABhAHMAcwB3AG8AcgBkACEAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>UABhAHMAcwB3AG8AcgBkACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Admin</Description>
<DisplayName>Admin</DisplayName>
<Group>Administrators</Group>
<Name>Admin</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:d:/=%20software/iso's/lic/en_windows_8_enterprise_x64_dvd_917522/sources/install.wim#Windows 8 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Everything goes fine, until is comes to the deployment of the VDI machines and the answer file is called. It fails with the following error:
PS N:\> \\dc01\isos\New-VirtualDesktopCollection.ps1
Unable to retrieve the details of the virtual desktop collection.
+ CategoryInfo : WriteError: (:) [Start-RDVMRollout], RDManagementException
+ FullyQualifiedErrorId : StartRDVirtualMachineRollout,Microsoft.RemoteDesktopServices.Management.Cmdlets.StartRDVirtualMachineRo
lloutCommand
+ PSComputerName : localhost
CollectionName Type Size PercentInUse
Pooled Managed... PooledManaged 0 0
writeErrorStream : True
OriginInfo : localhost
Exception : System.Management.Automation.RemoteException: Unable to retrieve the details of the virtual desktop
collection.
TargetObject :
CategoryInfo : WriteError: (:) [Start-RDVMRollout], RDManagementException
FullyQualifiedErrorId : StartRDVirtualMachineRollout,Microsoft.RemoteDesktopServices.Management.Cmdlets.StartRDVirtualMachineRolloutCo
mmand
ErrorDetails :
InvocationInfo :
ScriptStackTrace :
PipelineIterationInfo : {}
PSMessageDetails :
Without the answer file parameter is runs perfectly, BUT the VDI machines get the OOBE.... That's not what we want off course....
This link (http://support.microsoft.com/kb/2747656?wa=wsignin1.0) and other sources tell me that when i set the regkeys i can find a log in c:\windows\logs, but there is
nothing. I looked on the management server and the connection broker.
The only thing i could find in the event viewer was this:
The XML input specified for the VM Provisioning job is not in a valid format. Error: 0xC00CEE03
Input XML:
<?xml version="1.0"?>
<rdvp:RDVProvisioning xmlns:rdvp="http://www.microsoft.com/rdv/2010/05/">
<rdvp:ProvisionPoolRequest><rdvp:Job>
<rdvp:Action>Create</rdvp:Action>
<rdvp:OnError>Stop</rdvp:OnError></rdvp:Job>
<rdvp:Pool><rdvp:Name>Pooled_Managed_W</rdvp:Name>
<rdvp:Type></rdvp:Type>
<rdvp:VhdType>DiffDisk</rdvp:VhdType>
<rdvp:SaveDelay></rdvp:SaveDelay>
<rdvp:Version></rdvp:Version>
<rdvp:MARK_HA>No</rdvp:MARK_HA></rdvp:Pool>
<rdvp:Vm>
<rdvp:BaseVmLocation>\\RDSCB01\RDVirtualDesktopTemplate\Pooled_Managed_W\IMGS\__3</rdvp:BaseVmLocation>
<rdvp:LocalVmCreationPath>E:\_VDI</rdvp:LocalVmCreationPath>
<rdvp:LocalGoldCachePath></rdvp:LocalGoldCachePath>
<rdvp:SMBShare></rdvp:SMBShare>
<rdvp:EnableVmStreaming>0</rdvp:EnableVmStreaming>
<rdvp:RunVMsFromSMB>0</rdvp:RunVMsFromSMB>
<rdvp:NamingPrefix>Pooled-Win8</rdvp:NamingPrefix>
<rdvp:NamingStartIndex>1</rdvp:NamingStartIndex>
<rdvp:Domain>lab.local</rdvp:Domain>
<rdvp:OU>OU=VDI,OU=Computers,OU=Kamer 2101,DC=lab,DC=local</rdvp:OU>
<rdvp:ProductKey></rdvp:ProductKey>
<rdvp:UnattendXml>
<![CDATA[<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
</component>
</settings>
</unattend>]]>
</rdvp:UnattendXml>
</rdvp:Vm>
<rdvp:HyperVHosts>
<rdvp:HyperVHost>
<rdvp:Name>hyper02.lab.local</rdvp:Name>
<rdvp:NumberVms>3</rdvp:NumberVms>
</rdvp:HyperVHost>
</rdvp:HyperVHosts>
</rdvp:ProvisionPoolRequest>
</rdvp:RDVProvisioning>----------------------------------------------------------------------Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Admin
Source: TerminalServices-SessionBroker
EventID: 1549
Level: Error
User: NETWORK SERVICE
Task Category: MS VM Provisioning Plugin
Computer: RDSCB01.lab.local
I hope we can get this working, thanks in advance everybody!
Regards,
Bart

Hi Bartsp34ks,
I'm trying to make a powershell script like yours.
But at some point I receive this error:
System.Management.Automation.RemoteException: VM ASD-1: The data area passed to a system call is too small. (Exception from HRESULT: 0x8007007A)
My Powershell script is:
$CollectionName = Read-Host 'What Name should the Collection have?'
$Description = Read-Host 'Type a description of the Collection'
$OU = Read-Host 'In which OU should I put the Collection?'
$ConnectionBroker = Read-Host 'What is the Connection Broker Name? (use FQDN)'
$Sysprep = Read-Host 'Type the Unattend file location'
$DesktopAllocation = Read-Host 'On which RD Virtualization Host server should I create the Collection?'
$DesktopAllocationNR = Read-Host 'How many Virtual Desktop would you like?'
$NamePrefix = Read-Host 'What is the Prefix Name?'
$NameSuffix = Read-Host 'What is the Suffix Name?'
$UserGroup = Read-Host 'Which User Group can use the Collection?'
$UserProfile = Read-Host 'How big can the ProfileDisk be?'
$TemplateServer = Read-Host 'What is the RD Host that has the Virtual Desktop Template? (use FQDN)'
$TemplateName = Read-Host 'What is the Virtual Desktop Template Name?'
$UserProfilePath = Read-Host 'What should be the User Profile Path?'
$StorageType = Read-Host 'How should be stored?'
$StoragePath = Read-Host 'Type the Path'
New-RDVirtualDesktopCollection `
-CollectionName $CollectionName `
-Description $Description `
-OU $OU `
-ConnectionBroker $ConnectionBroker `
-PooledManaged `
-CustomSysprepUnattendFilePath $Sysprep `
-VirtualDesktopAllocation @{$DesktopAllocation=$DesktopAllocationNR} `
-VirtualDesktopNamePrefix $NamePrefix `
-UserGroups $UserGroup `
-MaxUserProfileDiskSizeGB $UserProfile `
-VirtualDesktopTemplateHostServer $TemplateServer `
-VirtualDesktopTemplateName $TemplateName `
-UserProfileDiskPath $UserProfilePath `
-StorageType LocalStorage `
-LocalStoragePath $StoragePath `
-Force `
-Debug
$error[0]|format-list -force
Thanks for help

Creating a personal virtual desktop collection - no existing virtual desktops listed

I have 2 windows server 2012 hosts in a failover cluster. This cluster is for RDS and VDI. Attempting to create a virtual desktop collection and there are no existing virtual desktops to select, even though i have created many from a template
via System Center VMM 2012 sp1.

Hi,
Thanks for your comment. Sorry for late response. Do you got any solution?
Please check below link for detailed information and try to reconfigure and verify whether it getting worked or not.
Windows 8 / Windows Server 2012: VDI Personal Desktop Collections
http://blogs.technet.com/b/askperf/archive/2012/11/01/windows-8-server-2012-vdi-personal-desktop-collections.aspx
Personal Virtual Desktops
http://blogs.msdn.com/b/rds/archive/2009/11/16/personal-virtual-desktops.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Windows Server 2012 Pooled Virtual Desktop collection GetVMstate issue

I am trying to create a Pooled Desktop collection with my Powered off VM and it errors out The
virtual desktop must be in a stopped state: Could not identify the state of the virtual desktop. Ensure that the RD virtualisation host server is available on the network and the virtual desktop is shut down
In the debug logs it shows.
Component RdmsModel: GetVMstate for Vm Win7_BaseVM failed with error 16386
Component RDExceptionHandler: Could not identify the state of the virtual desktop. Ensure that the RD Virtualization Host server sunflower-1.HYPERQA.NUTANIX.COM is available on the network and that the virtual
desktop Win7VMSF is shut down.
Please help on resolving this GetVMState issue.

Hi Krishna,
Thank you for posting in Windows Server Forum.
When you are configuring RDVH initially, please see that you have meet prerequisites. Remember that you need these pre-requirements:
• Database based on SQL Server 2008 R2
• Static IP Address for all Broker
• Round Robin DNS
• All RD Broker must be members of AD Windows Group (es. RDCB Server Group)
• The group must be insert into SQL Server as sysadmin ONLY for the DB creation. After that DB will be created give the db_owner permission only for their DB
More information.
Windows Server 2012 R2: Unable Add New VDI Template
In addition, we need all RD Broker must have the same SQL Native Client as main SQL Server (es. SQL Server 2012 SP1). The Connection Broker server's computer account MUST be a member of the local administrators group on the Virtual Host (RDS Host) machine and
then reboot the server. Finally check the result.
Windows Server 2012 Virtual Desktop Template Issue
Hope it helps!
Thanks.
Dharmesh Solanki

How can I make the popup with empty fileds and create new record?

I would like to use a popup to create new record.
I created a af:popup by drag and drop a VO from data control to jsff. then, I created a button and place a af:showPopupBehavior. I was able to popup window by click the button.
however, the window filled with the information from the 1st record. and when I select a record in table and click popup, the popup is filled with that record.
How can I make the popup with empty fileds and create new record by saving the popup?
Thanks

You can have edit and new buttons, in the PopupFetchEvent identify button source (using popupFetchEvent.getLaunchSourceClientId()) if new button clicked clear the binding using below code.
If you want to see empty fields, in the popup PopupFetchEvent clear the input component bindings.
resetBindingValue("#{bindings.<componentid>.inputValue}", null);
    public static void resetBindingValue(String expression, Object newValue) {
        FacesContext ctx = FacesContext.getCurrentInstance();
        Application app = ctx.getApplication();
        ExpressionFactory elFactory = app.getExpressionFactory();
        ELContext elContext = ctx.getELContext();
        ValueExpression valueExp = elFactory.createValueExpression(elContext,expression,Object.class);
        Class bindClass = valueExp.getType(elContext);
        valueExp.setValue(elContext,newValue);
    }

Previous computer crashed without my Adobe CS3 Design Standard for Macintosh application being uninstalled, I'm having issues with the CS3 on my new Macintosh laptop. Please help!

Since the previous computer crashed without my Adobe CS3 Design Standard for Macintosh applications being uninstalled, I'm having issues with the CS3 on my new Macintosh laptop. Please help, I've tried using the online "contact us" with no success, unable to get in contact with a tech support agent that can assist me.

CS3 is too old to run on a new Macintosh laptop, sorry. You'll have to purchase CS6 or a Creative Cloud subscription.

Having issues with phone calls on my new phone.

Having issues with phone calls on my new phone. Other user is hearing echoes or nothing at all. This seems to be a common issue on here. VERY annoying! Anything seem to fix this problem?

I had similar issues - Turns out it was a hardware problem or bad antennae - Call the tech support number and they can do some testing to determine the issue. They might be able to give you a replacement if you do it quickly.

Unattend.xml parsing/merging issue with SCVMM 2012 R2

Hi all
I have a problem with a new install of SCVMM 2012 R2. I have created templates for 2008 R2, 2012 and 2012 R2. I have an issue with the unattend.xml losing some of its configuration when the 2012 and 2012 R2 templates are built, this issue however doesn't
occur on a 2008 R2 template build.
I have generated unattend.xml files for all 3 OS's using System Image Manager in the latest AIK using the original install.wim from each OS media.
In the unattend.xml file I have specified language settings, and a few other bits but the issue I have is when I configure autologon with local admin and password. I specify a logon count of 1, I also specify a GUIRunOnce command in SCVMM and not the answerfile.
The problem is the resulting merged unattend.xml has a logon count of 999 and no GUIRunOnce command. I have tried different variations where I specify GUIRunOnce in the xml and not SCVMM, applying the autologon to the Template or Guest OS profile and
all end with the resulting xml with logon count of 999 and no GUIRunOnce. If I remove the autologon part then GUIRunOnce gets parsed and works correctly.
As mentioned this only happens with Server 2012 and 2012 R2, 2008 R2 works correctly.
Any ideas?

Hi Kevin
I am struggling with the same thing during bare metal installs of Hyper-V hosts. In my case I have managed to narrow it down to the language settings in the oobe pass. If I include them, parsing of the unattend file halts (without an explicit error anywhere)
and the host fails to join the domain. Could you try to leave out the language settings in oobe pass and see if it then completes as expected? Would be interesting to see if it actually is the same issue with a slightly different flavour :)
EDIT: Got a bit further now with the new release of WS2012 R2. All the testing I've done has been with the 05182 build. Stumbled across KB2913316 which stated that a new build (31419) was released december 11th. Allthough the KB does not directly apply to our
issue I thought I'd give it a go, so I went about building a new vhdx-image. Low and behold - the first test went smoothly applying all the settings in the unattend file! I'm going to continue testing to make sure the successful run wasn't just a fluke.

Measurement Computing USB-DIO96H driver issue with Labview 2012 SP1 on Windows 7 x64

Is anyone else having issues with measuremetn Computing's USB-DIO96H driver in Labview 2012 SP1. It throws warnings in Labview when loaded that are unresolvable as you can't save to the DLL driver file. Also it regularily crashes Labview randomly. I am not impressed with their driver. Anyone have any suggestion other than replacing with NI-DAQ solution, which I am working on?

I've taken a look and I don't see any drivers available for that device on ni.com. There are two potential workarounds that would both involve building your own driver:
1. Write a LabVIEW application that calls functions on the DLL you downloaded from Measurements Group
2. Write a LabVIEW application that addresses the device using NI-VISA and serial communication.
Some resources if you choose to go down that path:
http://www.ni.com/devzone/idnet/development.htm
http://www.ni.com/white-paper/3271/en/
http://www.ni.com/white-paper/3009/en/
Hope this helps!
Rob B
FlexRIO Product Manager

RDS - Issue using Windows 10 build 9926 as Virtual Desktop Infrastructure on Hyper-V 2012 R2

We currently have a production Windows 8.1 as a VDI/RDS on Hyper-V 2012 R2. On testing the last build of Windows 10 (98??) we had no issues deploying this in same RDS as pooled desktops.
The latest build 9926, although correctly sysprep-ed (either by removing AppX modern apps that have been updated, or not connecting the template to the internet), the build is only ever partially successful. Some VMs build others do not, and the ones that
build cannot be managed via RDS/Server Manager, functions such as logging a user off with server manager, result in an error. (WTS API failed)
Build Error on connection Broker - Microsoft-Windows-TerminalServices-SessionBroker
VM host [HOSTSERVER05] failed to execute VM Provisioning operation [Task: To perform post processing actions at VMHostAgent:] for virtual machine [VDI-W10-57] in pool [VDI_Advanced_Te], Error: [Error code: 0x88130221.]
Any guidance on how to troubleshoot this would be greatly appreciated, although I suspect something regarding the auto-deployment/unattend and management systems though RDS no longer works with the latest Windows 10 build.
Already posted this in the
Windows Insider Program site, but was asked to re-post here. Thanks

OK, I've carried out some more testing on the client site and have been able to move a couple of existing VMs from their 2008 R2 Hyper-V server to the new 2012 R2 server.
Both VMs are Windows 7 SP1 with the RDP 8.0 update installed and I can connect to them from a Thin Client running RDP 7.1 and a laptop running RDP 8.0.
When I add the RemoteFX vGPU to them both I can still connect from both devices but, as suggested, when connecting from the laptop with RDP 8.0 I don't get the vGPU performance (but the vGPU is still shown in the device manager).
It all looks good at the moment but I'm still concerned as to why I was unable to connect to the first VM I moved over (it was complaining about a error in the License network communication or similar).
I'll keep testing and post anything else that might be useful.
Cheers for now
Russell

How I solved issues with Mail.app and Spotlight

Even though my upgrade from Tiger 10.4.10 to Leopard was painless, the new OS X did have a few issues that had bothered me:
*Mail.app: * Every now and then, the app would behave like on its first startup, saying it needs to import my mail before I can work with it. What's more, at times I've had the phenomen that messages would appear empty on the preview pane and sometimes even when being opened.
*Spotlight: * Even though I let the indexing finish on the first day of working under Leopard, every now and then it seemed to start all over. First, I thought it's the NAS being indexed but it just went on to restart indexing each time I thought I had let it finish.
*Free disk space: * I tried to bring the usage of my homedirectory down so I would have enough free disk space to switch FileVault off and then back on so I could start using TimeMachine. But whatever I did, the free disk space just wouuldn't inrease - it just stayed the same (yes, I did let the system recover space on shutdown).
The *free disk space* issue made me think there was a problem with my disk but repeated runs with the Disk Utility yielded nothing...not for about a month. Yesterday I got some warnings about 'damaged but not repaired' but according to an Apple doc those could be safely ignored.
Somebody suggested to apply the combo update for 10.5.1 as that could solve some issues so I went ahead - after all, the update had already been applied earlier so just re-installing wouldn't hurt much, right?
Wrong.
The install of the combo update went smoothly, FileVault recovered some space on shutdown but upon restart I couldn't log in anymore: My homedirectory was damaged. The friendly OS X Leopard offered to repair it but soon later reported back that it failed doing so.
Now, to cut a long story short - deleting the affected user's account and using a different user on the same machine (without FileVault) solved any issues I've had. Mail now works like a charm (despite 40k+ messages with attachments), spotlight doesn't restart all it's indexing and disk space is shown correctly again. Also the odd corrupt file copy I had experienced occasionally (especially with large files) was gone.
My advise to anyone who didn't de-activate FileVault under Tiger to make the switch to Leopard: Even if you think it worked, switch it off and let Leopard set it up again. You may think things went right...but the above shows that there may be issues with it that you may blame other apps for...but they're probably not guilty at all.
I don't think the combo update actually caused FileVault to turn corrupt, it was just what broke the camel's neck. While it's no fun to lose your homedirectory, I'm glad the underlying issue finally came to light.

Thanks to this thread, it's been solved.
https://bbs.archlinux.org/viewtopic.php?id=97653

HUGE issues with I Pod Touch and new software

Christmas Day I opened I tunes to load some new CD's for my hubby and I. It said I needed the new I Tunes, so I downloaded it. Procedeed to get CD's loaded and plugged in hubby's I pod (it's about 6 years old and wheel style) it synced and was done in no time. I then plugged in my 3 year old I pod Touch, the system said it too needed an update, so I procedeeded with the IPod update. Towards the end, it said it was unable to complete the update (error 1602 and again later error 1604). It then locked up the Ipod and wiped it out. I have spent 2 days doing ALL the various steps I can find ANYWHERE to fix the error. The forums ALL say it's my computer and USB issues. I have done ALL the steps numerous times to "repair" the issue with NO luck it still says error 37 when I try to install the USB driver ( the port is an "enhanced" 2.0 port). I took the same cord and I pod downstairs to my daughters comuter that is running a version of Itunes 10.5.1 I think, It restored my I pod to the factory settings and it now turns on and has all the information to start to configure it again. So, took it BACK to my computer thinking that now the restore/update is complete that my computer should "see" the I pod again. NOPE! It still has the SAME problem. I have tried to install an older version of Itunes and it will not let me as the library has been "created by a newer version of I tunes". I am NOT a computer person at all and all the items I've tried have NOT worked. It is obviously NOT my comupter having USB issues as my daughters much older computer not only found the Ipod, but was able to restore/update it. I HAS to be the new ITunes 11.1 version. I have over 2500 songs on my I pod and depend on it at work as I have no radio reception.
I am at my wits end and very angry.
I run Windows XP on an older computer, but as I mentioned, my daughters older version of I tunes not only found the I pod, but restored it and updated the software. I want MY Library back on MY I pod so I need to use MY computer.
Any SIMPLE easy to follow ideas to fix this once and for all would be greatly appreciated. I have done all the USB steps and uninstalled/reinstalled and did the recovery mode and all those steps so many times. It still won't read the "driver" on the I Pod touch.
Thanks for any help.

I guess it's 4th Generation, I have no idea, it's a 32G and I've had it 3 years now.
Her computer runs Windows XP as well. It's an even older computer, the ONLY difference is that I did NOT update ITunes to her computer. Problem is, MY library is on MY computer.
I know it's an issue with I Tunes itself based on the fact my husbands older I pod will sync just fine to our library after th new I Tunes updates. It is JUST my Ipod touch.
I cannot go back to an older version of Itunes either because the library was "created in a newer version"

Issues with Advance Table Add Row New Row not work in some scenarios.

Hi,
Wondering if there's any issue with Advanced Tables where it does not create any rows. I don't know if anyone tried this or not. I have one OA Page with Advanced Table and a button that when clicked open a new OA Page in a POP-UP Window. The pop-up page conatins one textbox where u enter a data and this gets saved in one of the VO's transient attribute. Now on the ase page if you don't click a button to open a pop-up page you can Add New Rows in the Advanced Table by clicking Add Row Button. But as soon as you open a popup window and close it Add New Rows button doesn't work and is not creating any new rows. Basically page stops working. Both the POP-UP and the base page share the same AM but have different controllers.
POP-UP page is a custom page that I open giving the Destination URI value in the button item and target frame _blank.
I even tried creating rows programmatically for Advance Table but this too doesn't work once u open a pop-up. Also I have used pageContext.putTransactionValue in the pop-up page and am checking and removing this in the base page.
Any help is appreciated.
Thanks

anyone

[SOLVED]Issue with Postfix sending to external mail addresses

I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
myhostname = mail.sendingdomain.com
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
mydomain = www.sendingdomain.com
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
myorigin = $mydomain
append_dot_mydomain = no
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
inet_interfaces = all
#inet_interfaces = loopback-only
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = localhost
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
default_transport = error: Local delivery only!
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
alias_maps = hash:/etc/postfix/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = $alias_maps
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/bin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

Reader causing issues with dropped underscores in courier new font

When converting a microsoft word document in 2013 or 2007 to a PDF is causing issues with dropped underscores. It only seems to happen in courier new. For instance if I have _someCode, when converting this over to a PDF file I will sometimes see _someCode and sometimes I will see someCode. If I open this file in a different pdf reader then it looks correct 100% of the time. If I copy and paste into another application then the underscore shows. This is a major issue for people putting code into a PDF document as underscores are important and courier new is what we often use.

I love how quick you are to throw Microsoft under the bus. Often it is their fault. In this case I believe you are 100% wrong and absolutely short sighted to ignore this. As I said in my original email, which you apparently missed, I have tried this in multiple PDF viewers and Adobe Reader is the ONLY reader that misses the underscores. Foxit, PDF Exchange and Sumatra all render it perfectly. Adobe reader missed 6 underscores in my document that has 18 underscores. 30% of the time in this document Adobe Reader makes the underscore invisible. And if I switch the zoom to 100% instead of 148% (which is the default for me for some reason) then Adobe Reader misses 7 of them. This doesnt occur in the other readers. Blame Microsoft all you want but the simple fact is that Adobe Reader has issues reading courier new's underscores. It needs to be fixed.

(Solved) Issue with 2012 & 2012 r2...Creating New Virtual Desktop Collections Fails

Similar Messages

Maybe you are looking for