SSIS Deployment VS 2013

HI,
I've got an SSIS solution file with project deployment model in VS 2013 and would like to deploy that to SSISDB on different environments.
All these days I followed the regular way to create a project in SSISDB and deploy it to that. Now want to find out if i can automate this process and so got some questions
1. Can we automate the process of creating a project on SSISDB based on our SSIS project name?
This will be like when we do a deployment it should check if the project exists or not on SSISDB based on our SSIS project name, if the project exists we just deploy the packages in the project and if the project does not exists in SSISDB it will
create that project and deploy the packages.
2. Can we also automate the process of creating environments?
In traditional way we manually create the environment variables under environment tab of SSISDB, but can we make that also as part of deployment? Like when we are releasing to Dev server we look if that particular Dev variable exists on that server,
if it exists we just update the existing stuff and if it does not exists we just create it.
Thanks!

I found a series of this blog posts has the answer, e.g. creating the Environment http://blogs.msdn.com/b/dataaccesstechnologies/archive/2013/10/08/ssis-2012-automation-part-2-create-environment-map-it-to-project-and-package-level-parameters-and-assign-reference-to-project.aspx
Checking if folder exists can be done by say trying to apply a different variable value and if it fails then it does not exists, but there are may be better ways.
Arthur
MyBlog
Twitter

Similar Messages

Deploying Office 2013 with Group Policy

I would like to deploy Office 2013 using group policy. I am new to group policy so am looking for some advice and guidance on the best way to deploy. I would like to deploy with no interaction with the user but yet display a message so that they
know not to open Office. I would also like to create a custom registry setting so that if I need to re-install, all I have to do is delete the registry setting. I have tried a group policy for installing with OCT settings (Basic, Suppress
Model checked, No Cancel checked, Completion Notice checked) and modifying the Config.xml (<Display Level="Basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />) but I can not get it to display
the installer screen so that users know it is installing. It does display the screen when running the setup.exe manually. I have a setting in the OCT that creates the registry setting and that is working correctly. My group policy is set to run the
below bat file at startup in the Computer Configuration.
setlocal
REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************
REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
set ProductName=Office15.Standard
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer="\\xxxxxx\setup.exe"
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\xxxxx\Logfiles
REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************
IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)
REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto Office) else (goto End)
REM If 1 returned, the product was not found. Run setup here.
:Office
%DeployServer%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal
Any advice or guidance would be greatly appreciate on how to get a pop up message while software is installing or if there is a better way to deploy.

> but I can not get it to display the installer screen so that users know
> it is installing. It does display the screen when running the setup.exe
> manually. I have a setting in the OCT that creates the registry setting
> and that is working correctly. My group policy is set to run the
> below bat file at startup in the Computer Configuration.
Check http://gpsearch.azurewebsites.net/#2308 - if this is enabled, you
will not be able to show "anything" in startup scripts...
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Deploy Office 2013 using Group Policy

Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and have
the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
How do we automate the deployment process using a group policy?
Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
avoid having to go around and help each user activate the software as well.
We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
Thank you!

Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and
have the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
How do we automate the deployment process using a group policy?
Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
avoid having to go around and help each user activate the software as well.
We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
1. Because Office (in all forms) requires setup.exe to orchestrate the installations, classic Group Policy Software Installation (which requires an MSI file) is not suitable. This has been the case since Office2007. If you are constrained to use GP, you
will need to use GP Startup Scripts. There is guidance for this, in the Office resource kit library on TechNet.
http://technet.microsoft.com/en-us/library/ff602181(v=office.15).aspx
2. Retail editions of Office, typically require you to login to the Microsoft Account where the license is associated, to validate the Office license. If you are using a product key method instead, you can use the PIDKEY element in your configuration.xml
http://technet.microsoft.com/en-US/library/jj219426(v=office.15).aspx
3. You'll need to tackle this yourself (there is no way to do this via C2R configuration). You could include the relevant uninstall-previous-version logic within your GP Startup Script (as a step prior to installing Office C2R). You'll need to cater for
whatever previous-versions might exist in your environment, and whatever the relevant uninstallation methods are for each previous-version.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Deploy Office 2013 - Uninstall Office 2010

Hello,
I am planing to deploy Office 2013 and created a MSP File (Setup /admin) for the silent Installation - everything works fine - except the uninstallation of Office 2010. In the OCT I´ve selected the Option to remove previous Versions of Office. I can
remeber that this works perfect in Office 2010 to remove Office 2007 too.
But in Office 2013 this doesn´t work anymore, the installed applications wizard (appwiz.cpl) Shows both Version of Office are installed. What is the best way to remove the old Version silently and install Office 2013? I would like to have all in one
"Application" deployed via SCCM 2012 SP1.

Have you looked at this document, or it's online equivalents:
http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
In the section "Setup command-line options for Office 2013", they say:
/uninstall [ProductID]
Runs Setup to remove the specified product from the user’s
computer. Look up the value of [ProductID] in the Setup.xml
file for the product that you want to modify.
Example
\\server\share\Office15\setup.exe /uninstall ProPlus
where:
Office15 is the root of the network installation point.
ProPlus is the
[ProductID] ([ProductID]
is equal to the ID attribute of the
Setup element listed in
\\server\share\Office15\ProPlus.WW\setup.xml), where
ProPlus.WW is the location of the Office Professional Plus 2013 installation files.
You can customize the
/uninstall option by using it with
/config and a modified Config.xml file. This is necessary if you want to run a
“silent”
uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for user interactions, even when files are being used.
To run a silent uninstall
Using a text editor, edit the following element attributes in the
\\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml file:
<Configuration Product="ProPlus">
<Display Level="none"
CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" /> </Configuration>
At the command line, use the following syntax:
\\server\share\Office15\setup.exe /uninstall ProPlus /config \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml
Note:
In Office 2013, just as in Office 2010 and Office 2007, you cannot use the Setup.exe command line to set Windows Installer properties, such as
PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked
and unsupported properties, see Setup properties in Office 2010.
The information also applies to Office 2013.
Office Customization Tool (OCT) in Office 2013
Config.xml file in Office 2013

MICROSOFT DEPLOYMENT TOOLKIT 2013 DO I NEED LICENSE TO INSTALL THIS SOFTWARE IN MY COMPUTER

TO INSTALL MICROSOFT DEPLOYMENT TOOLKIT 2013 DO I NEED ANY MICROSOFT LICENSE,
I HAVE WINDOWS 7 & 2008 R2 LICENSES.
Many Thanks & Best Regards, K.SURESH

Hello Suresh,
MDT 2013, itself, doesn't require any license to install (apart from your OS license). Please see the below link:
http://www.microsoft.com/en-in/download/details.aspx?id=40796
if you plan to use MS System Center ZTI for deployment, then you would require a licensed system center installation (along with a licesnsed back end SQL installation). However, MDT won't require any license.
Hope that answers you query. Please mark this as answer if it answers your query. Please upvote.
Regards,
Rajesh

Deploy exchange 2013 with current Exchange 2007 organization

Dear All
our company will update exchange 2007 to exchange 2013, on AD site we already update Forest functional level and Domain functinal level to Windows 2003 ( can not up to windows 2008 yet because have some ad that run windows 2003 server
) but one thing that I'm not sure, between migration we can not full tranfer mailbox form exchange 2007 to exchange 2013 in one time, we need to migrate on night time manybe one day we can migrate only 100 user per night, my question is
1. which exchange 2013 server role that we will install first ( mailbox or CAS)
2. on migration time, can we let's user used exchange 2007 to main of OWA and SMTP or not? we need all user's mailbox tranfer to exchange 2013 complete first after that we will switch OWA and SMTP

1. Mailbox, or install both on the same server at the same time. (Edited: First I said CAS, which used to be true, but now you need the Mailbox role to run PowerShell, so you have to install Mailbox first. Consider a dual-role server,
however, because there aren't a lot of cases where you need separate CAS and Mailbox role servers.)
2. You cannot. Exchange 2013 mailbox users must use the Exchange 2013 CAS. You can have users use their respective CAS while migrating, but that requires two sets of URLs and is therefore more confusing for the end user. I recommend planning
to deploy Exchange 2013 CAS, a legacy URL for Exchange 2007, and switch your hostnames to Exchange 2013. This is all spelled out in the Exchange 2013 documentation.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

SCCM 2012 - Deploying Office 2013 Application - Setup Errors

dear SCCM admins,
i am trying to test deploying office 2013 to users in my company. i made the application and deployments. the application appeared in the software center and in the application catalog.
The problem is whenever a user "which is not a local administrator" tries to install this application, it gives me the setup errors message saying "You must have administrative privileges to install or uninstall this
product."
Is there any specific configuration to make to overcome this behavior???
appreciate your suggesstions
M.Zakaria

As you can see from the screenshot you need to add the ProductID after the uninstall command.
See here for finding the ProductID
http://blogmines.com/blog/2012/07/21/how-to-check-version-of-office-2013-products/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Deploy Office 2013 with language pack

Hi,
We want to deploy Office 2013, for this I followed the tutorial:
http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
In the first step I need to make an MSP file, but this file doesn't get used in the deployment? I think this is a fault in the tutorial.
Also the uninstall string is setuP.exe /uninstall. Is this correct?
Second we want to deploy the dutch language pack with SCCM 2012, but I can't find out how. The package need to be installed but Office 2013 still need to be default language English.
Can someone help me out with this?
Thanks in advance.

Some troubleshooting tips:
Run the installation command locally using SYSTEM account (Get psexec.exe, open cmd, run "psexec.exe -s cmd", this will open a new command line window with SYSTEM privilege, try running your installation command there)
Check the Office 2013 installation logfiles to see if your configurations are correct, more info on that here:
http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx
After those two steps are ready and you're sure your installation command works, you try it with ConfigMgr
With ConfigMgr, check %windir%\ccm\logs\ -folder for AppEval.log, AppEnforce.log and AppDiscovery.log, more info on these logfiles you can find here:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/26/new-logs-in-configmgr-2012-client-logs.aspx

Deploying office 2013 Professional plus with SCCM

Hello,
I want to deploy office 2013 with SCCM 2012. I want to make an package but how can i
download the office 2013 complete version ?<o:p></o:p>

Hi,
As far as I know, Microsoft now only provide MSI-based Office installer for Volume licensing Office. If you are a Volume Licensing customer, you can download the media via the Volume Licensing Service Center:
http://www.microsoft.com/licensing/about-licensing/office.aspx
More reference about how to deploy Microsoft Office 2013 using SCCM 2012:
http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
Thanks,
Ethan Hua CHN
TechNet Community Support

Deploy Exchange 2013 , Lync server 2013 and shrepoint server 2013

Hi dears ,
I have a deployment requirement in which I have to plan for deploy Exchange 2013 , Lync server 2013 and SharePoint server 2013 on premise for 500 user and for one organization , now I have been asked to provide the software and hardware requirement
for this deployment .
so I wonder , is there any guide or link to find the hardware and software requirements for this deployment ?

Hi,
You can refer to the link below about the hardware/system requirements for Lync Server 2013:
https://technet.microsoft.com/en-us/library/gg398438.aspx
Note: it is not supported to install Lync Server in the same computer with DC, Exchange Server and SharePoint Server.
If you want to deploy Lync Server, you’d better read the guide firstly before deploy it:
https://technet.microsoft.com/en-us/library/gg398616.aspx
For the deployment of Exchange 2013 and SharePoint 2013, you can also post case on Exchange and SharePoint forum, and there are more experts will help you:
Exchange 2013:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
SharePoint 2013:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=sharepoint
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Deploying Office 2013 x64 - feature installation state msp not applying

So I created my MSP with setup.exe /admin and configured a number of options in it. I saved the msp as "1Office64bit.msp" and saved it into the Updates folder. I also have a service pack for Office 2013 in the Updates folder.
I created an SCCM application to deploy office. My deployment installation program looks like this - setup.exe /config proplus.ww\config.xml
During my SCCM Build and Capture task sequence Office 2013 installs, the updates apply, and all of the settings in the MSP apply except for one. I specificed in the msp feature installation states to NOT install the Outlook feature, but it's not working?
Also - as a test after the task sequence completes, I run "msiexec /p \\pathtomsp\1Office64bit.msp - and it removes Office like it should. But I don't know why this doesn't happen during the initial installation?

You should use either a config xml file or an MSP during the installation of Office (2013). In your current command line it looks like you're trying to use both. As you saved the MSP file in the updates folder, simply specifying setup.exe should be enough
to start the installation and let it use the MSP.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
So I tried just running setup.exe and it doesn't seem to be working either. I verified in the ccm appenforce.log that the install command was just setup.exe (so the change made it to the client) but Outlook was still installed.
I'm going to try changing it to setup.exe /adminfile to see if that works.

Deploy Lync 2013 in phases

Can someone shed some light in this ? I really appreciate.
We currently have OCS 2007 (non R2), and planning to upgrade to 2013. We understand the choices of path of migration. However we want to understand if we can deploy 2013 with the the same features t we have today (IM and presence), and then add on other
features at a later stage. So this would look like this:
Phase 1: IM and presence
Phase 2: conferencing
Phase 3: AV conferencing
Phase 4: Dial-in conferencing
I understand at some point with Dial-in conferencing we have to setup FEs, so do we have to setup all the servers when we deploy in phase 1? How scalable it is if we want to expand/shrink the feature sets?
Thanks.

Hi,
Agree with Thamara.
The FE Server (or Standard Edition Server if it is Standard Edition) is the core Server roles for Lync Server 2013, and runs many basic Lync Server functions. After you install FE Server and BE Server (Standard Edition Server) and enable the related
function such as conferencing, you can use the function. IM and presence function is enable by default. If you want to use dial-in conferencing function, you need to collocate FE Server with Mediation Server or deploy Mediation Server alongside.
More details:
http://technet.microsoft.com/en-us/library/gg398536.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

SSIS Deployment in 2012/2014

Hi, I upgraded SSIS packages from 2008 R2 to 2014 and deployed to IntegrationServicesCatalogs->ssisDB. Now I m trying to use DTExec to schedule the packages in SQL Agent. I saved the package configurations to SQL Server table. Can someone help in the
below command? I m getting the error "Cannot find the folder" when I run the package. All the packages are deployed into SSISDB->GBI Folder->GDM Project.
Would appreciate any help, THank you!
"C:\Program Files\Microsoft SQL Server\120\DTS\Binn\DTExec" /SQL "\SSISDB\GBI\GDM\Master Load.dtsx" /SERVER "GBIVCST01" /CHECKPOINTING OFF /REPORTING E /CONNECTION Admin;"Provider=SQLNCLI11;Data Source=BRIDCDW01\BRIDCDW01;Persist
Security Info=True;Password=GBI1;User ID=G_BI;Initial Catalog=GDMConfiguration1"

>>>> I saved the package configurations to SQL Server table.
Where to? I mean a database? It is possible the Agent cannot read the data? Do you run it locally?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Content Deployment Sharepoint 2013 Standard or enterprise

Hi,
Is content deployment feature(from one farm to another) a part of Sharepoint 2013 standard edition or enterprise edition?
Thanks

Not sure about content deployment source but cross site publishing is only available in SharePoint 2013 Enterprise edition, i suggest you to go for enterprise edition for safe side.
SharePoint feature availability across on-premises solutions
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer.

SSIS Deployment VS 2013

Similar Messages

Maybe you are looking for