The File is too large for the destination file system

One of my user came to me and told me that he was unable to transfer a file (big  size file) to his external drive. He even bought a new one just for that - unfortunately, still failed. The error was :

The file <File Name> is too large for the destination file system.

as always, mark the key point there : file system.

Issues :
User was not able to copy large file to external drive due to above error.

Troubleshooting 

1.  Right click at Computer > Manage
   
   
   
2.  Computer Management console appeared. Go to Storage > Disk Management
   
   
   
    
3.  At the right side, you will see more or less this screen. Note the Free Space for the external drive was so large, so logically there should not be any issue to copy any files. At the same time, please also note at the File System type (FAT32)
   
   
   
   
4. If we look at the disk, the format also listed as FAT32

Resolution :

1.  Copy all files inside the external storage to another location, as a backup. Next steps will erase all data inside the storage, so keep a copy of those files is a MUST.
   
   
2.  Go to Computer Management, and right click at the storage. Click Format
   
   
   
   
   
   
3.  This message pop-up, press Yes.
   
   
   
   
   
4.  This window will pop-up. You can see the File system was currently set to exFAT.
   
   
   
   
   
5.  Change it to NTFS, and press OK.
   
   
   
   
   
6.  This message box pop-up, press OK
   
   
   
   
   
7.  Formatting…
   
   
   
   
   
   
8.  Formatting completed. The storage format changed to NTFS
   
   
   
   
   
   
9.  Try to copy the file again, and it will go thru successfully.
   
   
   
   
   
   

Read More

Unable to Access VMware vSphere Client Using Domain ID

In normal implementation, it is always a best practice to provide permission per group, rather than per individual ID. Simple reason is, it is easy to administer and manage. Therefore, it was what I did in one of my vCenter implementation, but I could not make it work. It just did not allow me to login using my Domain ID (which configured as part of Local Administrators members in vCenter server), although local ID (part of Local Administrators members as well) worked as expected.

Issues :
Error while connecting to vCenter Server using VMware vSphere Client. Error is :

Error Connecting

The vSphere Client could not connect to 

"vCenter Server Name"

You do not have permission to login to the server :

"vCenter Server Name"

 

Troubleshooting 

1.  Assigned appropriate domain ID (MyDomain\DomainAdminID) to a Domain Group (MyDomain\Domain Admins)
2.  Assigned that Domain Group to Local Administrators in vCenter server
3. (Double kill!) Assigned that Domain ID (MyDomain\DomainAdminID) to Local Administrators in vCenter server.
   
   
   
4. Configured Local Administrators with Full Admin Role in vCenter Permissions. Note that above Domain ID was not configured here. Local ID (.\ctxadmin) that will be used to test also not be configured here.
   
   
   
5. Tried to access vCenter using that domain ID, error prompted
   
   
   
   
   
6. Tried to access vCenter using local ID, successful
   
   
   
    
7.  Session with local ID.
   

Resolution :

It seems that starting from vSphere 5.5, configuring domain IDs/groups to local groups will cause the issue. Based on VMware KB  : 

Resolution

 This is an expected behavior.

To resolve this issue, give explicit permissions to Users or Groups from their respective Identity Sources. For example:

• Only populate Local OS groups with Local OS users or groups
• Only populate Active Directory groups with Active Directory users or groups

In order to do so :

1.  Add User ID / group to vCenter. Choose the domain, search the ID / group, and add them accordingly.
   
   
   
   
2.  Able to access, no error
   
   
   
   
3.  Session active with AD user ID.
   

Reference 

• http://blogs.vmware.com/vsphere/2013/09/vcenter-single-sign-on-5-5-not-recognizing-nested-active-directory-groups.html
• http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059528

Read More

vCenter 5.5 - Unable to Grant Permission to Domain ID - No Domain Listed

One fine day, someone came to me and asked, " I can't add domain users to vCenter. Can you help?" So, when I checked, I found this :

So yes, no domain listed there. So when I asked in detail, it seems this was a new deployment, vCenter just being created. Which really helped me to narrow down to root cause.

Issues :

Unable to Grant Permission to Domain ID - No Domain Listed 

Troubleshooting 

1. Login to vCenter using default admin ID ( administrator@vSphere.local ). These steps shall be done from Web Console rather than vSphere Client.
   
   
   
   
    
2.  Click at Administration
   
   
   
   
3. Click at Single Sign-On > Configuration. So as we can see here, only vSphere.local and vCenterServer (Default) are configured in Identity Sources. It means, these are the only domains which can be authenticated to.
   
   
   

Resolution :

1.  Click at Add Identity Source.
   
   
   
   
2.  Depending on the environment, appropriately choose identity source type. For this example, it is Active Directory  (Integrated Windows Authentication).Key in the Domain Name and all required info.
   
   
   
   
   
3.  Once done, you will see the new source listed here.
   
   
   
   
   
4. Newly added domain will be listed here.
   

Read More

The Trust Relationship Between This Workstation and The Primary Domain Failed

This is one of the common issue happen to PVS environment, IF the environment is not properly configured. The trust relationship will failed, if the password expiration days is  set below than computer account password updates. For example, if you set the password to be expired in 5 days, and computer account password updates set for 7 days, the password will then expired 2 days before renewal. Therefore, either disable password expiration, or properly set these 2 options according to Corporate Security policy.

Issues :

PVS : The Trust Relationship Between This Workstation and The Primary Domain Failed

Troubleshooting 

1.  Accessed to the VDA, could not authenticate using domain ID. 
2. Convert the VDA to Private mode / Create new version under Maintenance mode, unjoined and rejoined to domain. Put the VDA to Standard Mode / promote to Production, issue persisted.

Resolution :

1.  Shut down the target device.
   
   
   
   
2.  Right click at it, go to Active Directory > and choose Reset Machine Account Password...
   
   
   
   
3.  Correctly choose Domain as well as the Organization Unit, and press Reset Account
   
   
   
   
4. Resetting target device
   
   
   
   
    
5.  Target Device successfully reset
   
   
   
   
6.  Bring up the target device and try again.
   

Read More

How To : StoreFront Factory Reset / Rejoin Citrix StoreFront to Server Group

In some situations, you may need to unjoin a StoreFront server from an existing server group, and join the server to a different server group. However, after you remove it, there is no option to add it back. You will see this screen at your StoreFront server.

So, what it The easiest way? Reinstall StoreFront!. 

However, there is another cool way to do this, especially if you want to show off in front of your customers (no, I have never done this), or if you want to flaunt your expertise in front of your juniors (never done this as well).

Description :
StoreFront Factory Reset / Rejoin Citrix StoreFront to Server Group


How To Do :

1.  Close all opened / active Storefront consoles. You will get error if there is active session. Launch PowerShell as Administrator.
   
   
   
   
   
2.  Type asnp Citrix*
   
   
   
   
   
3.  Browse to %Program Files%\Citrix\Receiver StoreFront\Scripts
   
   
   
   
4.  Run ImportModules.ps1
   
   
   
   
5.   Modules imported
   
   
   
   
6. Run this command : Clear-DSConfiguration
   
   
   
   
7. Command completed.
   
   
   
   
8.  Close PowerShell, and launch StoreFront. You will get the option to join to existing server group back.
   

Reference :

• http://support.citrix.com/article/CTX200239

Read More

Disabling drive mapping on Server 2008

In previous post, I mentioned on how to disable drive mapping on Server 2003 via GPO. In this post, I will show on how to disable drive mapping on server 2008.

Description :
Disabling drive mapping on Server 2008


How To Do :

1.  Access to GPMC, edit the intended GPO. Browse to Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection
   
2. Click at ' Do not allow drive redirection '. That is our target setting
   
3. Right click at it, and press Edit
   
4.  Choose Enabled, press Apply and OK.
   
5.  You can double confirm the setting by checking at ICA-TCP and RDP-TCP Properties. They are now checked, and grayed out.
   
   
   
   
6. And this is the explanation by Microsoft on the GPO setting.
   

Read More