working in the field, as they have from XenMobile Migration 9.0 to 10.1 XenMobile we learned more than a few hours and checks given need attention. Here are some of our observations
observation. 1:
In XDM 9.0 if the name of the SQL Server is configured to only the host name (eg: sql1) and NOT with the FQDN of the SQL server (eg :. sql1.mydomain.com), you will have a problem with the migration occur
Resolution:
update C: Program files (x86) Citrix XenMobile Device Manager tomcat webapps zdm WEB-INF classes ew-config.properties file as the FQDN of SQL Server will (have 4 positions in the same file updated), to save the changes, before migration Introduction
properties that need to be updated to their / are .:
pooled.datasource.url = jdbc: jtds: sqlserver: // sql1.domain.com: 1433 / xxxxxxxxx
= pooled.datasource.hostname sql1.domain.com
audit.datasource.url = jdbc: jtds: sqlserver: //sql1.domain. com: 1433 / xxxxxxxxx
= audit.datasource.hostname sql1.domain.com
———————————————————————————————————————————————————————
Observation 2:
While migration perform you need to use exactly the same username as displayed while performing ZipIt !! Step.
———————————————————————————————————————————————————————
Observation 3:
Make sure that you in NetScaler Gateway Add enrollment FQDN -> Global Settings -> Configured domains for Clientless Access domains allowed
———————————————————————————————————————————————————————
Observation 4:
checks:
- Verify custom Store name in AppController, setting , becons.
- Check if AppController FQDN in uppercase letters (in V4 + fixed)
- Check the domain alias in LDAP config
- Run to check a comparison whether the 9.0 environment, if you have managed more than one LDAP. save
- Custom name works in 9.0 and 10.3 not 10.1
- Store name with spaces in 9.0
- Name of Business working with spaces will not work in 10.1 and 10.3
- If there are any spaces in the memory, they plan to 9.0
——————————————————————————————————————————————————————–
Observation 5:
checks:
- Update a note of the time zone settings Set in 9.0, the same in 10.3
- Check if there are any windows 8.1 devices and WorxHome version
- Check whether there are any "." (Points) in group names in XM 9.0
——————————————————————————————————————————————————————–
Observation 6:
- Before and / or At the time of migration
- [1945009delete] browser cache, Chrome browser is preferred
- Check if the customer has installed for MAM V6 license server
- Check if the customer new DMZ IP has load balancing virtual server and for migration load Balancer
- Disable load balance 443 virtual Server
- Disable load balance 8443 virtual Server
- Disable NetScaler Gateway virtual Server
or
- set to load 443 and 8443 ports on firewall balance Virtual Server
- Block 443 port on firewall NetScaler Gateway Virtual Server
Note: No users should have access to XenMobile have 9.0 environment
——————————————————————————————————————————————————————–
Observation 7:
- after migration - XenMobile 10.1
- Ensure Time and time zone, they put it equal to such xenmobile 9.0
- Certificates Check
- licenses Check
- Make sure Worx branding (Store name)
- cluster Check the settings, activate SSL Offload if cluster
- firewall settings Make sure you enable Port 80
- Verify LDAP edit, and save
- ensure appS
- ensure devices and the status of devices
- delivery groups Check
- ensure ew-config.properties updates of 9.0
- XenMobile HealthChecks perform
- Run NetScaler Gateway Health check
——————————————————————————————————————————————————————–
Observation 8:
- after migration - for NetScaler Verify
- 1 load balancing virtual server install fresh, 2 load balancing of virtual servers for the migration, we call them create as
- XMS load Balancer, 8443
- AppController load Balancer, 443
- DNS A record for AppController FQDN Recalling AppController Load Balancer
- is the service new XMS server
- create DNS A record for XMS (enrollment) FQDN Recalling XMS Load Balancer
- The service is new XMS server be
- AppController certificate should AppController Load Balancer
- Add / Check XMS STA NetScaler- Gateway VIP [1945010gebunden]
- Add / Check storefront STA NetScaler Gateway VIP
- Add / Check XMS FQDN less access domain is added in client
——————————————————————————————————————————————————————–
Observation 9:
post Migration: NetScaler configuration is not visible in XMS
. Problem:
- Data Migration in the XMS 10.1 was successful, but NetScaler configuration show not under settings up
- We found that the data was in the DB on the new XMS because the data migrated.
- What and where was the problem?
- had the web address below showcase a [1945012gefundenwurde]: 0 (example in the figure below)
——————————————————————————————————————————————————————–
Observation 10:
after migration: WorxStore takes more than 5 minutes to open
Edition:
- data migration is successful.
- users of Android and iOS are able to authenticate
- If on WorxStore knocking, there is a latency of about 5 min observed.
- guidelines on all NSG revisited were observed no problems.
- There are no errors in device protocols have been found
- What and where was the problem?
reason
- storefront server was configured when no storefront first existed
- WorxStore will ping over perform 3 tests and wait for a response from the server storefront after it expired.
- see also practices as enrollment fails @ MAM..etc
. Solution:
- to the XenApp / Desktop showcase Config from the XMS
——————————————————————————————————————————————————————–
Observation 11:
after migration - include user to particular domain could not log
User. managed belonging to one of four domain could this domain managed under "Users OU" filled box on MDM 9 not login, LDAP setting the OU had to be information base.
reason
post migration to the LDAP settings for that particular domain verification was watching, that the MDM 9.0 LDAP "users OU" was worn over config XMS 10.x as "user base DN" in the context of migration, causing the problem
. Solution:
modified to the details in the XMS from OU full base DN (root context) "DC = xxxxxx, DC = xxx, DC = xx" this Problem solved.
. NOTE: The issue has been detected and will in the next version 6 (V6) of the migration tool
fixed——————————————————————————————————————————————————————–
Observation 12:
after migration - not launch Published Applications
reason: ..
- XenApp and XenDesktop STA were NSG VIP not added
- In this case the customer a new NetScaler for the migrated environment was
——————————————————————————————————————————————————————–
Observation 13:
after migration - can not V6 license server
- Port Connect 7279 was not open although port was 27000 opened.
- In this case the customer is setting up a new V6 license server.
——————————————————————————————————————————————————————–
Observation 14:
post Upgrade - Number of licenses incorrectly displayed
the reason that the customer (correctly appears 10.3.0) because of SA (Subscription Advantage) date when the licenses fewer licenses in 10.3.5 as the previous version's looks. All licenses with a Subscription Advantage date prior 2016.0301 [March 1, 2016] is not displayed on the console for 10.3.5. Likewise, all licenses with Subscription Advantage date is prior 2015.1019 [Oct 19, 2015] are not displayed on the console for 10.3. we received from the license files from customers, we have seen that all licenses are valid for Poseidon only 500 licenses for Theseus valid
. Solution:
contact license server team, you can get a consolidated license file by the license reallocting
FYR. Case # 71064244
——————————————————————————————————————————————————————–
Observation 15:
. Problem: After migrating XMS server for a continuous reboot is
Have Proxy enabled on the AppController, either the username or password has to hold a special character in it. If YES , recommended the following steps.
- Undo / Remove the proxy of AppController setting the CLI use.
- Once again export the Support Package encrypted form.
- Perform the migration process.
- After you have successfully performed the migration, you can enable the proxy, configure it again with the new XMS CLI.
0 Komentar