Adobe Element Licensing in disaster recovery

Hi,
We have Adobe Element installed locally on various pc's in our company. We are currently designing a DR solution and an am interested in how to successfully implement this with Adobe Elements V2. We are proposing loading Adobe Elements in a DR Citrix farm.
Reading through the EULA, you can either
1) Run Elements locally or
2) Assign the elements license to a device and have that device access Elements through citrix.
If we install elements in DR citrix environment, would we then have to re-purchase Adobe Element license for every device that could access Elements, as we have used up our install license by installing them locally??
David

i guess the main question is do you want to define this license server as a secondary RDS license in your GPO or will you manually change the GPO option in the event of a DR? is this DR site actively accessible or it will only become available once
DR has been invoked?
as for compliance...not sure how that would work, you would probably use the same license activation on your DR as you would in your production but whether that's abiding by the EULA is something I've never encountered to answer, someone else here might
know

Similar Messages

Disaster Recovery-MS SQL Server 2008 License

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...
Yes you will need license for SQL server in DR environment.
Licensing is wast and non technical question so it will be best answered by Licensing expert.
For more detailed information regarding to the license issue, please call 1-800-426-9400Call: 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00
P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to
Find contact information in your locations.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I have a valid copy of Premiere Elements 11 that does not open past the Elements 11 Organizer Adobe Software License Agreement

My copy of Premiere Elements 11 will not open. I'm on a PC with System 7. When I double-click on the PE11 desktop icon, the window opens that says Elements 11 Organizer Adobe Software License Agreement. I select English (North America) and "Accept". The window disappears but then reappears again and again. I have tried uninstalling and reinstalling from the disk and from the download. I have also tried a clean boot and have restarted numerous times. It accepts my Serial Number OK, but I can't seem to get beyond this step. Any help would be appreciated.

stechasingleton
Consider uninstall, free ccleaner run through (regular cleaner and registry cleaner parts), reinstall with antivirus and firewalls disabled.
CCleaner - PC Optimization and Cleaning - Free Download
Significantly different from what you did already?
Have you looked at the antivirus interference in this?
Even after the uninstall/reinstall, you might explore deleting the Adobe Premiere Elements Prefs file, and, if that does not work, then
the whole 11 Folder in which it exists.
Local Disc C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
11.0
and, in the 11.0 Folder, is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 11.0
Folder in which it exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see
the complete path cited.
I have not seen that Organizer Adobe Software Licensing Agreement issue before and it does not quite fit in with the usual troubleshooting
drill. But the above is worth the try to rule in or out.
We will be watching for your progress.
Thank you.
ATR

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

Datafiles Mismatch in production & disaster recovery server

Datafiles Mismatch in production & disaster recovery server though everything in sync
We performed all the necessary prerequisites & processes related to DRS switchover successfully also our DRS server is constantly updated through logs application in mount state whan we opened DRS database in mount state it opened successfully however when we issued command
Recover database
It dumped with foll errors:
ora-01122 database file 162 failed verification check
ora-01110 data file 162 </oracle/R3P/sapdata7/r3p*****.data>
ora-01251 unknown file header version read for file 162
as I do not remember the exact name now
However upon comparing the same file at production(which was now in shutdown state) the file sizes were mismatching so we went ahead to copy the datafile from production to DRS in database shutdown state at DRS through RCP utitlity of AIX 5.3 since our Operating system is AIX 5.3
Though this remote copy was success
we again started database in mount state & issued command
Recover database
But still it dump the same error but now for another datafile in DRS
I mean I would appreciate if somebody could point out that despite our DRS was constantly being updated through our Production in terms of continuous log application before this activity logs were sync in both the systems also origlos,mirrorlogs & controlfiles were pulled from production system as it is infact the whole structure was as replica of production system , then why did datafile sizes mismatch??
Details
SAP version :- 4.7
WAS :- 620
Database :- Oracle 9.2
Operating system :- AIX 5.3

I am in a process of DR Planning.
My present setup :
O/S : HP-UX 11.31
SAP ECC 6
Oracle 10g Database.
I know about dataguard and i have implemnted same on our other application but not for SAP.
I have ame doubts and I request you to please guide me for the same.
1. SAP License key -- it required hardware key. So will i have to generate license key another hardware key i.e. for machine where standby database.
2. Database on standby site will be in manage recovery mode. Will I have to make any changes or any other file realted to SAP on standby host ? (some i know such as I upgrade SAP kernal, same i have to upgrade at standby host)
Will you give me some link related to document for DR

DR (Disaster Recovery) server installation.

Dear Experts,
We have one server for BI PRD. We are not using it at the moment. We wish
to carry out DR (Disaster Recovery) trial on this server. Regarding thiswe have following queries :
1. Do we require separate SAP License key for this server when setup forDR (already SAP license key exists for it as BI server)
2. We will re-install BI on the same server after our DR test so whetherwe need to regenerate License key for BI or not?
3. We have two R/3 PRD servers in HACMP mode in SAN. Can we take the
backup of R/3 PRD and restore it on DR Trial Server? If yes, whether we
will face any problem for existing PRD server?
4. Whether Existing PRD and Trial DR Server will clash or hang since
these will be in the same local network and SAN
Please advise.
Regards,
Kailas Padwale.
BASIS Team.

Hi,
As per your query you have not mentiones here what is your opreting system and whcih SAP verson you are using. If any one need related to implimentaion then we keep in mind to os,sap version,database etc.
Your Question: If you want to DR of PRD then you have to get my answer.
1. Do we require separate SAP License key for this server when setup forDR (already SAP license key exists for it as BI server)
ANS= Yes you can generated from SAP Site becasue now this is BI and you want to DR but for this you have not paid any thing to SAP its free.
2. We will re-install BI on the same server after our DR test so whetherwe need to regenerate License key for BI or not?
ANS=NO becasue you have to use only PRD copy you can not run BI here otherwise how can you say this is DR server. DR Server means you can copy in existing running server, in case you running server get down then within short period you can provide the solution. After rectificaton actual server you will shift in old one.
3. We have two R/3 PRD servers in HACMP mode in SAN. Can we take the
backup of R/3 PRD and restore it on DR Trial Server? If yes, whether we
will face any problem for existing PRD server?
ANS=You can restore backup but you have to take backup only one PRD server and restore it in DR. Just chang your IP Address and rest can be same. You will not face any issue on this if you run in the same network. I will recmond if you use database in DR server itself then good for your running system will not impect.
4. Whether Existing PRD and Trial DR Server will clash or hang since
these will be in the same local network and SAN
ANS= No because you will use seprate IP address and data will be in DR server not in SAN.
In case you need more help, pls get in touch.
Anil

I made an error asking to receive Windows product of Adobe Element 13 and Premiere while I needed the Mac Version. How is it possible to correct this error ? and what do I have to do if you accept ?

I made an error asking to receive Windows product of Adobe Element 13 and Premiere while I needed the Mac Version. How is it possible to correct this error ? and what do I have to do if you accept ?

Normally an Elements license is valid for both Windows and Mac systems. So you might only need to download the Mac versions of the applications and use your serial number to activate them.

How to replicate CDC on Disaster Recovery Database.

I have a scenario here.
In Case you have CDC installed on your main database. The changes are getting captured and you get the changes in the subscriber views.
In case your main database goes down due to some reasons. You cannot access even a single table of the database now you are to take an export dump to be taken to a different database.
In this case there is a disaster recovery database, wherein the tables and the number of records is same as the main database, since it is refreshed every now and then.
Is it possible to replicate the change tables with the archived log files present??
The mode of operation of CDC is Asynchronous Hotlog mode.
Please suggest the alternative for replicating CDC on a separate database, if one database is gone, without any miss in the changes.
Regards,
Uravesh Vora

moz44 wrote:
Hi guys, happy thanksgiving day to you all.
Some people say that it is possible to replicate a derby database running on one host to mysql running on another host. Has any of you have experience with that?That wouldn't be quite the same as for example replication on Oracle to Oracle.
But the following claims that it does what you want. No reason to suppose it doesn't. Look at the license carefully (I didn't look at it at all.) It basically supports any jdbc driver (two one for each source.)
[http://enterprise.replicator.daffodilsw.com/]
I would expect more problems with more complicated databases. But that is true with databases that have built in replication as well.

How to configure high availability and disaster recovery? And user authenticate

We are in the process of rolling out our online help which was created using Robohelp. In our initial rollout we will provide access to the files via our Client Portal which requires authentication. We are also planning for our next version where we intend to implement Robohelp server functionality.
Our IT team is looking at options on how to configure for High Availability and Disaster Recovery. It seems that Robohelp doesn't have any built-in functionality in this area. In addition we require that our users authenticate. The options for the server version seem to be more internally focused and we would need to solution the authentication using a third party.
Would anyone be willing to share their approach in these areas? Would you be willing to participate in a conference call with our IT Professionals?

Hello again
I see my good friend Peter replied to your LInkedIn post where you cross-posted the same question. For those here that have no clue what Peter stated, here it is:
What are you seeking to recover? Your projects? Your outputs? This sounds like a question more appropriate to Disaster Recovery consultants and far wider reaching than RoboHelp. To me it seems like a question your IT people should be asking direct to such consultants who would expect a fee for their advice.
I would agree with Peter's reply.
I'll also go further and ask what exactly is being done in this realm for the application? Help files generally are there to support an application on the server. So whatever you are doing for the applciation should also be able to be used for the WebHelp, FlashHelp or web based AIR Help files, no?
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

WLC Redundancy - Disaster Recovery

My questions is in relation to disaster recovery, for wireless. We have our main data center, in the US, with two 5508 controllers. We have a DR location, in Europe, with two 5508 controller. We're upgrading our 5508's to the 7.4 code, so that we can take advantage of the RP port for our controllers. With that said, is there a way to make the US and Europe controllers redundant? If there's a disaster, in the US, would the AP licensing, and AP's attach to the European controllers? Our AP's are set up with HA. I'm more concerned about the licensing flipping over to the DR controllers. I've tried researching this topic, and can't really find anything on it. Thanks!

If you can't use the RP port and configure SSO, then yes you need to have adequate licensing to support all the AP.
But if the AP fall from one DC to another, are the clients going to get the same IP? Failing across DC is most effective when you use FlexConnect, IMHO.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Need help for Disaster Recovery setup and configuration

Hi Gurus.
We are planning to have disaster recovery test plan. Normally we setup our network at another site and then restore data there and then do configuration and setup to run SAP system to new network.
But this is little more time consuming. We are planning to do something which will might save our time.
We want to create one Application instance on Central instance on current production server. This instance will be "deactivated" and will not run on production server.
When we will do the disaster recovery, we will restore CI filesystem to Disaster recovery network. That time this new application instance will aslo get copied. Once this is done, we just need to go to this instance and start SAP System. This way we will save our time of configuring the new instance and then starting it.
e.g
Production host -> prdhost1
Central Instance -> /usr/sap/P01/DVEBMGS00
and it's subdirectory: data, work, log, sec
create new application instance -> /usr/sap/P01/D03
and it's subdirectory: data, work, log, sec
create new instance profile -> P01_D03_prdhost1, START_D03_prdhost1
this configuration will be created but SAP instance will not be started. It will be copied to Disaster Recovery new site and in that new network , there we can start this new application instance.
Please let me know if we can do that ? if yes, are we going to face any issue in production?
Other than mentioned above, what FileSystem we need to take care for creating new instance?
Any help will be highly appreciated.
Thanks in advance
Best Regards,
Basis CK

Hi!
Sorry but your scenario is a little bit confusing.
Let me guess if I understood, you want to configure a "virtual" instance to be able to use it in case of DR.
I don't advise you to do things that way. Why not use virtual hosts and virtual instances like we do when implementing instances within a cluster or metrocluster.
You must have the license from DR server installed. I you use virtual hosts all DR issues like printers, logon groups, RFC groups, etc... will be solved.
If you use virtual hosts and virtual instances all you need to do is replicate the environment into DR site, restore the system and start production.
Of course... you are using UNIX and within UNIX world all these things are much easier.
Bear in mind that if you have JAVA instances then I think this is the only recommended procedure.
Cheers,
FF

Bought Adobe Elements 12 in retail, want to install it on ultrabook without DVD reader - solutions?

Bought Adobe Elements 12 in retail, want to install it on ultrabook without DVD reader - any solution? Possible to download and activate the license with the product key I have on the box?
thanks

yes, download the trial and activate with your serial number, http://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_elements

Hi, i have adobe elements 12 (downloaded) for windows 7 pc, but want to transfer it to mac (not keeping the pc). how to ?, please.

Hi, i have adobe elements 12 (downloaded) for windows 7 pc, but want to transfer it to mac (not keeping the pc). how to ?, please.

Download the Mac version and use your serial number to acrivate it. As long as your license is mulriplatform it should work.
PSE 10, 11, 12 - http://helpx.adobe.com/photoshop-elements/kb/photoshop-elements-10-11-downloads.html
PE 10, 11, 12 - http://helpx.adobe.com/premiere-elements/kb/premiere-elements-10-11-downloads.html

SharePoint 2010 backup and restore to test SharePoint environment - testing Disaster recovery

We have a production SharePoint 2010 environment with one Web/App server and one SQL server.
We have a test SharePoint 2010 environment with one server (Sharepoint server and SQL server) and one AD (domain is different from prod environment).
Servers are Windows 2008 R2 and SQL 2008 R2.
Versions are the same on prod and test servers.
We need to setup a test environment with the exact setup as production - we want to try Disaster recovery.
We have performed backup of farm from PROD and we wanted to restore it on our new server in test environment.Backup completed successfully with no errors.
We have tried to restore the whole farm from that backup on test environment using Central administration, but we got message - restore failed with errors.
We choosed NEW CONFIGURATION option during restore, and we set new database names...
Some of the errors are:
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified user or domain group was not found.
Warning: Cannot restore object User Profile Service Application because it failed on backup.
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Verbose: Starting object: WSS_Content_IT_Portal.
Warning: [WSS_Content_IT_Portal] A content database with the same ID already exists on the farm. The site collections may not be accessible.
FatalError: Object WSS_Content_IT_Portal failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
Warning: [WSS_Content_Portal] The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
RESTORE DATABASE is terminating abnormally.
FatalError: Object Portal - 80 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname.
FatalError: Object Access Services failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Secure Store Service failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
FatalError: Object PerformancePoint Service Application failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Search_Service_Application_DB_88e1980b96084de984de48fad8fa12c5 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Aborted due to error in another component.
Could you please help us to resolve these issues?

I'd totally agree with this. Full fledged functionality isn't the aim of DR, getting the functional parts of your platform back-up before too much time and money is lost.
Anything I can add would be a repeat of what Jesper has wisely said but I would very much encourage you to look at these two resources: -
DR & back-up book by John Ferringer for SharePoint 2010
John's back-up PowerShell Script in the TechNet Gallery
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

SharePoint 2013 Search - Disaster Recovery Restore

Hello,
We are setting up a new SharePoint 2013 with a separate Disaster Recovery farm as a hot-standby. In a DR scenario, we want to restore all content and service app databases to the new farm, then fix any configuration issues that might arise due to changes
in server names, etc...
The issue we're running into is the search service components are still pointing to the production servers even though they're in the new farm with completely different server names. This is expected, so we're preparing a PowerShell script to remove
then re-create the search components as needed. The problem is that all the commands used to apply the new search topology won't function because they can't access the administration component (very frustrating). It appears we're in a chicken &
egg scenario - we can't change the search topology because we don't have a working admin component, but we can't fix the admin component because we can't change the search topology.
The scripts below are just some of the things we've tried to fix the issue:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$local = Get-SPEnterpriseSearchServiceInstance -Local;
$topology = New-SPEnterpriseSearchTopology -SearchApplication $sa;
New-SPEnterpriseSearchAdminComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchCrawlComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $local -IndexPartition 0 -RootDirectory "D:\SP_Index\Index";
$topology.Activate();
We get this message:
Exception calling "Activate" with "0" argument(s): "The search service is not able to connect to the machine that
hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a'
in search application 'Search Service Application' is in a good state and try again."
At line:11 char:1
+ $topology.Activate();
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
Also, same as above with
$topology.BeginActivate()
We get no errors but the new topology is never activated. Attempting to call $topology.Activate() within the next few minutes will result in an error saying that "No modifications to the search topology can be made because previous changes are
being rolled back due to an error during a previous activation".
Next I found a few methods in the object model that looked like they might do some good:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$topology = Get-SPEnterpriseSearchTopology -SearchApplication $sa -Active;
$admin = $topology.GetComponents() | ? { $_.Name -like "admin*" }
$topology.RecoverAdminComponent($admin,"server1");
This one really looked like it worked. It took a few seconds to run and came back with no errors. I can even get the active list of components and it shows that the Admin component is running on the right server:
Name ServerName
AdminComponent1 server1
ContentProcessingComponent1
QueryProcessingComponent1
IndexComponent1
QueryProcessingComponent3
CrawlComponent0
QueryProcessingComponent2
IndexComponent2
AnalyticsProcessingComponent1
IndexComponent3
However, I'm still unable to make further changes to the topology (getting the same error as above when calling $topology.Activate()), and the service application in central administration shows an error saying it can't connect to the admin component:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.
Lastly, I tried to move the admin component directly:
$sa.AdminComponent.Move($instance, "d:\sp_index")
But again I get an error:
Exception calling "Move" with "2" argument(s): "Admin component was moved to another server."
At line:1 char:1
+ $sa.AdminComponent.Move($instance, "d:\sp_index")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : OperationCanceledException
I've checked all the most common issues - the service instance is online, the search host controller service is running on the machine, etc... but I can't seem to get this database restored to a different farm.
Any help would be appreciated!

Thanks for the response Bhavik,
I did ensure the instance was started:
Get-SPEnterpriseSearchServiceInstance -Local
TypeName : SharePoint Server Search
Description : Index content and serve search queries
Id : e9fd15e5-839a-40bf-9607-6e1779e4d22c
Server : SPServer Name=ROYALS
Service : SearchService Name=OSearch15
Role : None
Status : Online
But after attempting to set the admin component I got the results below.
Before setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation : E:\sp_index\Office Server\Applications
Initialized : True
ServerName : prodServer1
Standalone :
After setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation :
Initialized : False
ServerName :
Standalone :
It's shown this status for a few hours now so I don't believe it's still provisioning. Also, the search service administration is still showing the same error:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration
component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.

Adobe Element Licensing in disaster recovery

Similar Messages

Maybe you are looking for